I provided a patch to SHIRO-197 in case anyone wanted to build it themselves, but there are two important things I wanted to get in 1.1 that might delay it a little bit:
- Improving the AuthenticationInfo / HashedCredentialsMatcher implementations to support better salting techniques and - The new-and-improved JndiLdapRealm (with documentation) Any delay caused by those tasks would hurt anyone evaluating Shiro for the first time because of the bug, and we'd probably see more mailing list questions related to it. I'm especially worried about this since I'll be presenting to a lot of people tomorrow night and I wouldn't want a large influx of new evaluating users to be confused/frustrated. How long do you think it take for us to push out a 1.0.1 release (not including voting time) given that we're only changing 1 file? If it's small, do you think we could give it a shot? Les On Mon, Oct 11, 2010 at 4:32 PM, Kalle Korhonen <[email protected]> wrote: > On Mon, Oct 11, 2010 at 3:57 PM, Les Hazlewood <[email protected]> wrote: >> I think I might have found a critical bug relating to how INI sections >> manage property ordering. > > Hmm yes, I thought it was fairly apparent from SHIRO-184, filed two > weeks ago. If you ask on the user list whether you should release or > not, I'm sure somebody will say yes. I don't use the ini file > configuration myself and we can do the 1.1.0 release fairly quickly > but if you want to spend the time and practice releasing, I don't see > why not. Personally, I wouldn't go through the trouble though given > that 1.1.0 will follow so closely after. > > Kalle
