> I don't think we should merge this to 1.5
no, rather not.
> BTW, do you think this should be noted in the 1.6 release notes for
> people who are already trying out the new security code? I'm not sure
> how big an impact the changed property type will cause.
big. that's why i scheduled it for 2.0.0.
but after all the 283 implementation is still work in progress and Issue #
JCR-1588 has not been closed up to now. unless the spec is finalized there may be any kind of changes that break backwards compability.
listing in in the release notes may still be a good idea.