> > process. Given that we've had a long and large exposure to 1.0-SNAPSHOTs (I'd assume many Shiro users are using the snapshots),
I'd be inclined to keep it simple and start with blind releases and Not sure it matters, but I do want to note that I'm using 1.0-snapshots in production right now. I would guess that I'm not alone out there. For the most part it has been stable with only a few incidents where shiro updates caused a problem in my app. I would love to see a release based on something close to the current trunk to remove this instability. Also, the wicket-shiro project at wicketstuff can't be released until Shiro is in a maven repository. It has been commented out of the wicketstuff pom until a maven release is made, so I don't think many wicket devs are even aware of it or using it. Once a release is made, I will be able to finally release the wicket-shiro plugin to other wicket developers. I hope this will help increase awareness of the shiro project. Tauren
