[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [site] update release process (Was: Re: [VOTE] Release Commons Imaging 1.0-alpha1 based on RC1)

Hi Rob!

Thanks for the instructions, and for writing them so well and quickly!

Removed everything from the imaging's dist area first as you suggested. Then had a look at the new docs, and also at commons-text's pom.xml. Updated imaging's pom.xml.

Then produced the local artifacts first, and everything looked OK. Then used the next step to produce the staging repository. (did that a few times; first time dropping a release and re-rolling a new one...)

And it's amazing! It uploaded everything, with no errors, avoided uploading the .tar.gz and .zip files (sooo annoying) and also created the dist area.

Then closed the repository in the staging repo.

## Notes:

- The docs about the vote e-mail generation say target/vote.txt... copying and trying to do a `vim /target/vote.txt` failed, and then I realized it's actually `target/VOTE.txt` (nit-picking!)

- Also, the e-mail generated contained:

"We have fixed quite a few bugs and added some significant enhancements since Apache Commons Imaging 1.5...."

I mistakenly left the bc.version to 1.5, but just replaced the occurrences of 1.5 by 0.97-incubator, and mentioned that clirr was to be ignored as this was the first release of this new component (i.e. imaging != sanselan). Hopefully that's OK.

- I forgot to tag RC2, so it failed with

The Git tag commons-imaging-1.0-alpha1-RC2 commit for this RC is fatal: ambiguous argument 'commons-imaging-1.0-alpha1-RC2': unknown revision or path not in the working tree.

I proceeded to tag the current release with `git tag -s commons-imaging-1.0-alpha1-RC2`, and updated the text. My bad, don't think we need to update the docs for that.

- Maven artifacts URL had a variable that was not expanded? Maybe I missed something in my pom.xml?


Fixed the link to point to https://repository.apache.org/content/repositories/orgapachecommons-1395/org/apache/commons/commons-imaging/1.0-alpha1/


As this is my first release with this new plugin, and since I manually edited more than what's expected in the vote.txt, plus forgot the tag... it's likely I missed/messed something, so may roll one more release soon if necessary (plenty of time this weekend).

Vote e-mail sent, have a look if I followed the instructions correctly.

Thank you again!!

ps: Will look for the Slack link again... I don't have Slack on this computer... do you know if we have the link for the slack channel somewhere in the website/twitter/etc?

From: Rob Tompkins <chtompki@xxxxxxxxx>
To: Bruno P. Kinoshita <kinow@xxxxxxxxxx> 
Cc: Commons Developers List <dev@xxxxxxxxxxxxxxxxxx>
Sent: Tuesday, 30 October 2018 1:33 AM
Subject: Re: [site] update release process (Was: Re: [VOTE] Release Commons Imaging 1.0-alpha1 based on RC1)

> On Oct 29, 2018, at 7:24 AM, Rob Tompkins <chtompki@xxxxxxxxx> wrote:
>> On Oct 28, 2018, at 8:04 PM, Bruno P. Kinoshita <kinow@xxxxxxxxxx> wrote:
>> 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.
> I’ll try to work on this this morning (UTC-4) both on the [site] as well as sending the details over to you.

Hey Bruno,

Since you’re using [parent] version 47, you should be most the way there. I, on the preparing releases page, added the needed configurations: 


>From there you should simply be able to run

mvn -Duser.name=<your apache id> -Prelease -Ptest-deploy clean test package site deploy

to test the deployment (test SVN dist commit ends up in ./target/commons-release-plugin/scm), and

mvn -Duser.name=<your apache id> -Prelease clean test package site deploy

to run the deployment (assuming that your settings.xml has sufficient privileges). Note, this is also covered here: 


IMPORTANT: to get the svn distribution commit to properly work, make sure that https://dist.apache.org/repos/dist/dev/commons/imaging/ is completely empty.

Feel free to ping me on slack if anything arises. I do know that we’re 14 hours different in terms of timezones though.



> -Rob
>> Thanks heaps
>> Bruno
>> ________________________________
>> 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.
>> Cheers,
>> -Rob
>>> 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.
>>> Gary
>>>> 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:
>>>> https://dist.apache.org/repos/dist/dev/commons/imaging/IMAGING_1_0_RC1/
>>>> (svn revision 30460)
>>>> The Git tag commons-imaging-1.0-alpha1-RC1 commit for this RC is
>>>> 44f4b12dc3f5131944a9c147e1a8f0dc18360806 which you can browse here:
>>>> https://git-wip-us.apache.org/repos/asf?p=commons-imaging.git;a=tag;h=refs/tags/commons-imaging-1.0-alpha1-RC1
>>>> Maven artifacts are here:
>>>> https://repository.apache.org/content/repositories/orgapachecommons-1393/
>>>> These are the Maven artifacts and their hashes
>>>> commons-imaging-1.0-alpha1-javadoc.jar
>>>> (SHA1: 0f6c64af7dd7099024c5ecd9fd2632db04b1d719)
>>>> commons-imaging-1.0-alpha1-sources.jar
>>>> (SHA1: 12734288eca62bc87ac3b8efc77d66c80cd9a310)
>>>> commons-imaging-1.0-alpha1-test-sources.jar
>>>> (SHA1: 415cd0ff4af1c69d39b35c907ef29180ce4a03d6)
>>>> commons-imaging-1.0-alpha1-tests.jar
>>>> (SHA1: 9704b79c446e2a5b1f6c4ff7c09ac5a0383326af)
>>>> commons-imaging-1.0-alpha1.jar
>>>> (SHA1: b39f13c05550327501224cd2cbd02591c59a8bbb)
>>>> commons-imaging-1.0-alpha1.pom
>>>> (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:
>>>> https://dist.apache.org/repos/dist/dev/commons/imaging/IMAGING_1_0_RC1/RELEASE-NOTES.txt
>>>> http://people.apache.org/~kinow/commons-imaging-1.0-alpha1-rc1/changes-report.html
>>>> Site:
>>>> http://people.apache.org/~kinow/commons-imaging-1.0-alpha1-rc1/index.html
>>>> (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:
>>>> http://people.apache.org/~kinow/commons-imaging-1.0-alpha1-rc1/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. 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...
>>>> Thanks!
>>>> Bruno
>>>> ---------------------------------------------------------------------
>>>> 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