Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 74.125.82.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAJSjvwtEpB6xY5tvc4zFVP04xeHOFO7EqZiSD7Pm0HPnR1146w@mail.gmail.com>
References: <50E9F9F5.7050802@gmail.com>
	<CACZkXPx51+q_+hkW877PcKzitSm888_d+-2oTygKtDtYT9x8Ng@mail.gmail.com>
	<CAJSjvwtEpB6xY5tvc4zFVP04xeHOFO7EqZiSD7Pm0HPnR1146w@mail.gmail.com>
Date: Wed, 9 Jan 2013 10:53:55 +0000
Message-ID: 
 <CAOGo0VapEO-7F2f2S4dZHroeBJM8X=mtB-HOFVAyTktjdxsgEg@mail.gmail.com>
Subject: Re: [VOTE] Release of Commons Email 1.3 based on RC7
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On 9 January 2013 10:03, Thomas Neidhart <thomas.neidhart@gmail.com> wrote:
> On Mon, Jan 7, 2013 at 8:41 PM, Gary Gregory <garydgregory@gmail.com> wrote:
>
>> +1.
>>
>> I suspect we'll need another RC to deal with pub/svn when you actually try
>> to do the release because the usual place we put sites is now supposed to
>> be read-only.
>>
>
> my own +1.
>
> My understanding was that the old deployment process still works, but is
> not supported anymore by infra.

There are two aspects to this:
- whether the staging area is read-only protected
- whether the staging area is being copied to the public areas on www.apache.org

The latter was previously being done using a cron job.
If that has already been switched off, then the staging area can be
updated, but the changes won't be propagated.

[For projects which have been switched, the staging area will no
longer be directly writable as it will be maintained by SVN]

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org