On Fri, Apr 15, 2016 at 12:38 PM 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. 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. > You can refer to our main page on releases here at the ASF: http://www.apache.org/dev/release-publishing.html which links to the maven-specific steps here: http://www.apache.org/dev/publishing-maven-artifacts.html This outlines a process very similar to what I described above (with the exception that we're possibly using Git and not Subversion, but the concepts are the same).
