+1 to release (binding)
On Thu, Jan 19, 2012 at 2:55 PM, Kalle Korhonen <[email protected]> wrote: > On Thu, Jan 19, 2012 at 1:51 PM, Les Hazlewood <[email protected]> wrote: >> I was trying to be consistent with the actual release version number, >> since that is most relevant when perhaps needing to do a checkout (or >> perusal) from SVN at a later date. The 'shiro-root' prefix is a >> side-effect of maven, not something that should be reflected in SVN >> IMO. > > Our existing tags are at http://svn.apache.org/repos/asf/shiro/tags/ > and it's not consistent with the previous tag. It's not a > "side-effect", any of our sub-modules could technically follow an > independent release cycle. > >> i.e. I find this much better: >> trunk >> branches/1.2.x >> branches/1.3.x >> tags/1.1.0 >> tags/1.2.0 >> tags/1.2.1 > > I'm sure you are not proposing to change the root layout of our svn space? > >> Is the existing tag something that would prevent you from voting? I'd >> _really_ not want to do another release again (which I think I'd have >> to do to ensure the maven <scm> tags are consistent, right?). I've >> spent 4+ hours on this process already (fighting with the site plugin, >> gpg, re-releasing, etc) :/ > > In general, if we cannot release any given module by running mvn -B > release:prepare release:perform and have the release completed within > a few minutes, we are doing something wrong. If it's a matter of time, > I can fix it, addressing this issue shouldn't take more than 15 > seconds. > > Kalle
