Answers inline. 2017-11-06 7:08 GMT+01:00 Gary Gregory <[email protected]>: > The blocker part is that the VOTE email does not follow the process or the > format outlined on http://commons.apache.org/releases/prepare.html > > Specifically, > - the tag does not contain an "RC2" postfix (since this is the 2nd RC). > - there is not tag for RC1 so we've lost what we voted on for RC1 (too late > for that.)
It is fine I think to not have the tags since they are "dead tags" anyway. No need to recreate them now probably. > - the email does not contain the file names with hashes (see the email > Nexus sent you when you "closed" the repository.) Will need to check but seems our nexus is not accessible ATM > - the links to SVN resources do not contain SVN revision numbers (required > since SVN tags are mutable) r1809493 > > This is all fixable without an RC3, you just need to send a VOTE email that > follows the format in http://commons.apache.org/releases/prepare.html > > Gary > > On Sun, Nov 5, 2017 at 10:55 PM, Romain Manni-Bucau <[email protected]> > wrote: > >> Dist/Nexus is a manual step but ok. Rc creation is a blocker since it >> prevent to use maven tools - release plugin. Did we - as commons - already >> open a feature request to maven? >> >> Anyway dont think it blocks the release *now* so can we proceed? >> >> Also moving to git can solve it by design too since we dont need to push >> upstream the branch before the release is done. >> >> Le 6 nov. 2017 04:50, "Gary Gregory" <[email protected]> a écrit : >> >> > On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter <[email protected]> >> > wrote: >> > >> > > >> > > >> > > > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl <[email protected]>: >> > > > >> > > > Hi Gary, >> > > > >> > > > On 25.10.17 05:24, Gary Gregory wrote: >> > > >> Our process documented here http://commons.apache.org/ >> > > releases/prepare.html >> > > >> makes it pretty clear that the RC tag should be labeled as such and >> > > that a >> > > >> tag like "commons-jcs-2.2.1" should only be created after a VOTE >> > passes. >> > > > >> > > > as this release is created using the Maven Release plugin, the >> > automatic >> > > > process is to create a tag identical to the release version. The docs >> > > > you mention tell nothing about how to handle the RC case. Does the RC >> > > > tag need to be renamed, copied or re-created? >> > > > >> > > > BTW, there was no such request when I created the previous three >> > > releases. >> > > >> > > I agree, we shouldn’t be to picky, since releasing components is >> already >> > a >> > > PITA. >> > > >> > >> > I agree that the release process is a PITA. I've complained about it many >> > times before on this ML but I've never contributed a solution to improve >> > the process. >> > >> > I think there is talk of improving the commons build plugin... but I am >> not >> > sure how. >> > >> > Surely, having to publish to both "dist" and Nexus is a pain. >> > >> > Gary >> > >> > >> > > >> > > Benedikt >> > > >> > > > >> > > > Bye, Thomas >> > > > >> > > > >> > > > ------------------------------------------------------------ >> --------- >> > > > To unsubscribe, e-mail: [email protected] >> > > > For additional commands, e-mail: [email protected] >> > > > >> > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> > >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
