On 15 April 2016 at 17:38, James Carman <ja...@carmanconsulting.com> wrote: > On Fri, Apr 15, 2016 at 11:50 AM Benson Margulies <bimargul...@gmail.com> > wrote: > >> >> 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.
Not sure I follow why it is silly. > The fact that there's a > "tag" doesn't (or shouldn't) mean something has been "released" by our > PMC. This much is true, but the convention has always been to create the final tag to correspond to the approved source revision. And further, that such tags are immutable (which is now effectively true for Git). Therefore the tag can only be created once the release has been approved. > 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 Removing the tag is not possible for Git final tags. > numbers in the pom.xml files so that we can try again. Or, we could just > use the next version number. I think that is what Tomcat does. > 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. That is effectively what the final release tag is. We vote on the RC tag, and create the release tag from the successful RC tag. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
