What was the reason to rename the tag? If we ever have independently releasable modules, it gets confusing because the tag doesn't immediately tell you for which module it is. If you don't like the shiro-root name, let's change the module name, rather than omit it from the tag. I'd prefer renaming the tag to shiro-root-1.2.0 for consistency. Binaries are ok.
Kalle On Thu, Jan 19, 2012 at 11:39 AM, Les Hazlewood <[email protected]> wrote: > This is a call to vote in favor of releasing Apache Shiro version 1.2.0. > > The 59 issues solved for 1.2.0 (since the 1.1.0 release): > > https://issues.apache.org/jira/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+SHIRO+AND+fixVersion+%3D+%221.2.0%22+AND+%28status+%21%3D+Open+and+status+%21%3D+%22In+Progress%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true > > The tag to be voted upon: > https://svn.apache.org/repos/asf/shiro/tags/1.2.0 > > Staging repo for binaries: > https://repository.apache.org/content/repositories/orgapacheshiro-102 > > Project website (just for informational purposes, not to be voted upon): > http://shiro.apache.org/ > and maven static generated site (for informational purposes, not to be > voted upon): > people.apache.org:/www/shiro.apache.org/static/1.2.0 or > http://shiro.apache.org/static/1.2.0 once it propagates to web servers > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. Please do examine the source and binaries before > voting. > > [ ] +1 > [ ] +0 > [ ] -1 (please include reasoning)
