Return-Path: X-Original-To: apmail-struts-dev-archive@www.apache.org Delivered-To: apmail-struts-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27F1EE218 for ; Fri, 1 Feb 2013 10:10:13 +0000 (UTC) Received: (qmail 97484 invoked by uid 500); 1 Feb 2013 10:10:12 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 97095 invoked by uid 500); 1 Feb 2013 10:10:07 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 97049 invoked by uid 99); 1 Feb 2013 10:10:05 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 10:10:05 +0000 Received: from localhost (HELO mail-ob0-f178.google.com) (127.0.0.1) (smtp-auth username lukaszlenart, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2013 10:10:05 +0000 Received: by mail-ob0-f178.google.com with SMTP id wd20so3877377obb.37 for ; Fri, 01 Feb 2013 02:10:03 -0800 (PST) X-Received: by 10.182.23.20 with SMTP id i20mr8997319obf.44.1359713403932; Fri, 01 Feb 2013 02:10:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.93.7 with HTTP; Fri, 1 Feb 2013 02:09:43 -0800 (PST) In-Reply-To: References: From: Lukasz Lenart Date: Fri, 1 Feb 2013 11:09:43 +0100 Message-ID: Subject: Re: Removing old versions To: Struts Developers List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2013/1/31 Paul Benedict : > Is there a space issue that infrastructure is complaining about? No, they say it will not scale very well - but I think the problem is with Svn which is used to support SvnPubSub as each file must be committed to svn first and then it's checked out on the webserver with additional svn specific files. Anyway I've proposed something like this: /release/1.2.x /release/1.3.x /release/2.0.x /release/2.1.x /release/2.2.x /release/2.3.x and development versions /dev/1.x /dev/2.x When new version of 2.3.x branch is going to be released, it will point to /release/2.3.x and so on. Users can always download packaged versions of older docs. Regards --=20 =C5=81ukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For additional commands, e-mail: dev-help@struts.apache.org