Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <570CE061.7070901@apache.org>
References: 
 <CALhtWke2ghL2KVQzu7HD28f6cmOb=v-+OtACwPjnSiUipDJk_Q@mail.gmail.com>
	<570CE061.7070901@apache.org>
Date: Tue, 12 Apr 2016 13:13:22 +0100
Message-ID: 
 <CAOGo0VZpRsLss=-tj2W-ii8tNjrUzk97CxB4E3Wk+9PUiG0uCA@mail.gmail.com>
Subject: Re: [VOTE] Release commons-io 2.5 based on RC4
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8

On 12 April 2016 at 12:47, Mark Thomas <markt@apache.org> wrote:
> On 12/04/2016 12:42, Benson Margulies wrote:
>> We have fixed quite a few bugs and added some significant enhancements
>> since Commons IO 2.4 was released,
>>   so I would like to release Commons IO 2.5.
>>
>> NOTE: because this is just an RC, and because I'm not a PMC member,
>> I'm pointing to the release on Nexus rather than copying it to dist.
>> If this is objectionable, we can make the dist copy. I've borrowed

Sorry, don't like it.

>> this maneuver from the Maven project.

It's only dist/release that matters (and that is only updated when the
vote passes)

Much better to use dist/dev now, and include the URL/revision in the mail.

Then publishing can be a rename, rather than a copy from Nexus (which
would not be traceable)

> No objections to the process. Just to note you should now have write
> access to /dist/dev/commons, /dist/release/commons and
> /dist/test/commons
>
> If you could do a quick test (e.g. in /dist/test/commons) to confirm
> write access that would be great and if it doesn't work I'll have some
> time to fix it before you need to copy the release to /dist.
>
> Mark
>
>
>>
>>
>>   The official release (source zip file) for commons-io 2.5 RC4 can be found at:
>>
>>     https://repository.apache.org/content/repositories/orgapachecommons-1146/
>> /commons-io/commons-io/2.5-RC4/commons-io-2.5-RC4-source-release.zip
>>
>> It's MD5 is c8e14c99056c5b59104baa6f56406b94.
>>
>>   The Maven artifacts for testing can be found in
>> https://repository.apache.org/content/repositories/orgapachecommons-1146/
>>
>>   Details of changes since 1.1 are in the release notes:
>>     https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12322486&styleName=Text&projectId=12310477&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7Cbd5449774a37a4a86ee7a92f5dfa95db1a0691f2%7Clin
>>
>>
>>
>>   I have tested this with 1.6 using maven 3.0.4
>>
>>   The tag is here:
>>
>> https://svn.apache.org/repos/asf/commons/proper/io/tags/commons-io-2.5-RC4
>> (1738772)
>>
>>   Site:
>>     http://people.apache.org/~bimargulies/commons-io-2.5-RC4/
>>   (note some *relative* links are broken and the 1.2 directories are
>>   not yet created - these will be OK once the site is deployed)
>>
>>   Clirr Report (compared to 1.1):
>>     http://people.apache.org/~bimargulies/commons-io-2.5/clirr-report.html
>>
>>   RAT Report:
>>     http://people.apache.org/~bimargulies/commons-io-2.5/rat-report.html
>>
>>   KEYS:
>>   https://www.apache.org/dist/commons/KEYS
>>
>>   Please review the release candidate and vote.
>>   This vote will close no sooner that 72 hours from now, i.e. after
>> 0400 GMT 31-March 2010
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>>   Thanks!
>>
>>   bensn
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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