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

Re: [VOTE] Release Apache Commons RNG 1.1 based on RC5

On Thu, 2 Aug 2018 10:31:04 -0400, Rob Tompkins wrote:
On Aug 2, 2018, at 10:02 AM, Gilles <gilles@xxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Rob.

The generated release notes do not reflect the contents
of the current version of "changes.xml":


Not a blocker but a pity because the advertized release date
will be quite off and the 1.1 branch is slightly inconsistent.
I'd suspect that the release plugin is missing the command
to run the auto-generation...

One thing which I found handy in "doc/release/release.howto.txt"
(also in order to minimize the post-release adjustments) was:
If there have been changes committed in the master branch or the version branch since the creation of the release branch, there are two cases:

if all these changes must be included in version 1.0, merge "master"
 or the version branch into "1.0-release":

   $ git merge master

 or, if the version branch is called "RNG_1_X"

   $ git merge RNG_1_X

 if only part of these changes must be included in version 1.0,
 cherry-pick the required commits into the "1.0-release" branch:

   $ git cherry-pick commit-SHA

Is there a script to automatically verify the checksums?  Modular
projects tend to have a lot of files. ;-)
Do you contemplate making that check a part of the release process?

I’ve got something close with:





Could such a script be added in the vote email, as a convenience
for those who'd like to do that check too?
Otherwise, I'd tend to think that it's a tool/procedure that must
be integrated to the release process (upload to Nexus, then run
the script to ensure that what is there is what was sent).
I don't see the purpose of several people checking what one script



To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx