commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <>
Subject Re: Is there an missing bit in the instructions for making a release?
Date Fri, 15 Apr 2016 16:38:34 GMT
On Fri, Apr 15, 2016 at 11:50 AM Benson Margulies <>

> The problem is that this PMC does not want a tag named after the real
> (not RC) version to come into existence  until after the vote passes.
Well, that's the thing that is somewhat silly.   The fact that there's a
"tag" doesn't (or shouldn't) mean something has been "released" by our
PMC.  With the setup I use, I log into Nexus OSS and basically approve the
staging repository so that it can be officially released.  So, we could
create a staging repository for folks to vote (along with the corresponding
tag).  If the vote fails, we just drop the staging repo.  Now, we could at
that point decide that we want to remove the tag and fix the version
numbers in the pom.xml files so that we can try again.  Or, we could just
use the next version number.  I don't really care one way or another.  We
could even call out releases specifically by copying the tag to
"releases/foo-1.2.3" or something.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message