Re: [site] update release process (Was: Re: [VOTE] Release Commons Imaging 1.0-alpha1 based on RC1)
Will cancel the vote tonight, thanks for spotting that @Gary.
@Rob, thanks a lot for all the great work on the new plugin. I might be able to roll a new RC tonight, or during this week. Would you have a pointer to the some page with the commands I have to run to properly use the plugin and upload the right binaries and signatures, please?
Not in a hurry to cut the release, so if you are planning to write the docs this week, I'd be happy to review/try them for the imaging RC2.
From: Rob Tompkins <chtompki@xxxxxxxxx>
To: Commons Developers List <dev@xxxxxxxxxxxxxxxxxx>
Cc: Bruno P. Kinoshita <kinow@xxxxxxxxxx>
Sent: Monday, 29 October 2018 2:49 AM
Subject: [site] update release process (Was: Re: [VOTE] Release Commons Imaging 1.0-alpha1 based on RC1)
This is mildly on me for not updating the release docs recently. I’ll put that on my docket for the week.
PS. @Bruno solid work and many thanks for rolling the RC.
> On Oct 28, 2018, at 9:35 AM, Gary Gregory <garydgregory@xxxxxxxxx> wrote:
> Hello Bruno,
> Thank you for preparing the RC.
> MD5 and SHA1 are no longer acceptable per Apache for our dist server.
> Please use SHA256 or SHA512. Our Commons release plugin will create those
> for you. Nexus has different requirements and that is fine for now.
>> On Sun, Oct 28, 2018, 04:58 Bruno P. Kinoshita <kinow@xxxxxxxxxx> wrote:
>> We have fixed quite a few bugs and added some significant enhancements
>> since Sanselan 0.97-incubator was released,
>> so I would like to release Apache Commons Imaging 1.0-alpha1.
>> This will be the first release after the project was renamed from Sanselan
>> to Apache Commons Imaging. This is an alpha
>> release candidate.
>> Apache Commons Imaging 1.0-alpha RC1 is available for review here:
>> (svn revision 30460)
>> The Git tag commons-imaging-1.0-alpha1-RC1 commit for this RC is
>> 44f4b12dc3f5131944a9c147e1a8f0dc18360806 which you can browse here:
>> Maven artifacts are here:
>> These are the Maven artifacts and their hashes
>> (SHA1: 0f6c64af7dd7099024c5ecd9fd2632db04b1d719)
>> (SHA1: 12734288eca62bc87ac3b8efc77d66c80cd9a310)
>> (SHA1: 415cd0ff4af1c69d39b35c907ef29180ce4a03d6)
>> (SHA1: 9704b79c446e2a5b1f6c4ff7c09ac5a0383326af)
>> (SHA1: b39f13c05550327501224cd2cbd02591c59a8bbb)
>> (SHA1: 03697c87b9e18b5c69946712c31c3fd85cdde1ee)
>> I have tested this with 8 using Maven 3.5.4 on Ubuntu LTS.
>> Details of changes for 1.0-alpha1 are in the release notes:
>> (note some *relative* links are broken and the 1.2 directories are
>> not yet created - these will be OK once the site is deployed)
>> RAT Report:
>> Please review the release candidate and vote.
>> This vote will close no sooner that 72 hours from now,
>> i.e. sometime after 04:00 UTC 31-March 2010
>> [ ] +1 Release these artifacts
>> [ ] +0 OK, but...
>> [ ] -0 OK, but really should fix...
>> [ ] -1 I oppose this release because...
>> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
>> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx