hi jukka
As a general rule for getting fixes into the 1.0 branch; if you have a fix for an important enough issue that you'd like to still have included in the 1.0 release, do this:
thanks for the instruction
I don't expect to have too many changes in the 1.0 branch so apply your judgement on whether an issue is important and low-risk enough to be included in 1.0. We'll always have 1.1 for more improvements. :-)
right. but i'd like to limit api changes between 1.0 and 1.1 if possible. i knew about JCR-337 for some time before, but since the jcr-server contrib was not part of the original release plan i didn't feel any hurry for this. it's fine by me to include the jcr-server contrib in the 1.0 release but i feel there is the need for this change before the release. i'm sorry if that is cumbersome for you as release manager and move the release date. on the other hand i was a bit surprised, that all in a sudden the contribs were included in the release. thanks for you understanding angela
