Due to compatibility issues, we can't backport new features into older releases. We adhere to the APR versioning guidelines: http://apr.apache.org/versioning.html. This is done for very good reason - Shiro's perceived stability is critical for companies that use it. If we deviated from these guidelines, we risk incompatibility issues that could significantly hurt the image of the project.
For example, if we added it to a 1.1.1 release, and you upgraded to Shiro 1.2.0, your upgrade would fail (because this code was not present in the 1.2.0 release). This scenario breaks APR versioning upgrade semantics, which is why it would have to be added to 1.3.
Similarly, we can't add this to 1.2.1 because point versions (i.e. Major.Minor.Point) are expected to be both forwards and backwards compatible. That is, I must be able to use 1.2.8 and downgrade to 1.2.0 without compile-time repercussions. If a new major feature like this was in 1.2.1 and not 1.2.0 the downgrade would fail.
For these reasons, until 1.3 comes out, this module must be released independently of Shiro's release. But if we can get it in to 1.3.0-SNAPSHOT versions right now, that'd be great - I'm just looking for a more modern 'cut' of Deluan's code, presented by Deluan himself.
The reason this must occur is that Deluan does not currently have licensing information in his code in GitHub. As an Apache-managed project, we cannot copy code that isn't already associated with an Apache compatible license. Until Deluan licenses his GitHub project entirely as Apache 2 licensed, or he submits a patch to our Jira (which constitutes a valid ASF contribution), I can't copy it.
Deluan if you could give us an updated patch, I'd appreciate it!