I knew it was a good practice to update the svn tag - so I tagged this as ...-1-rc2. However, it seems that the Maven instructions for rolling back and redo-ing a release led me to expect that the release number would be the same. Maven instructions for releasing a Maven-based project at Apache, include a ref to this guide for testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html which says to purge your local repo (and any repository manager you might be using) after testing, to avoid keeping around a potentially failed release.
Because I "dropped" the only place where the previous "release" was staged (in the staging repo), no one can get that release anymore. But it is possible that users could forget to purge their local copies. As you note, bumping up the release number would avoid this. Thanks for your good mentoring :-) - much appreciated! -Marshall On 6/10/2010 10:27 AM, Jukka Zitting wrote: > Hi, > > +1 > > PS. It's good practice to update the version number of a release even > after a failed release candidate. This avoids the problem of someone > accidentally using an outdated version. > > BR, > > Jukka Zitting > > >
