Hi, On 3/9/06, Angela Schreiber <[EMAIL PROTECTED]> wrote: > > 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.
Agreed. The API change scores high enough on the importancy scale to warrant inclusion in 1.0. > 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. I didn't have jcr-server in the 0.9 release to keep it simple, but I did mention having jcr-server included already in the first draft of the 1.0 release plan. I'm sorry for not making more noise about that. If you are uneasy about including jcr-server in the release then I can drop it for now. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftsmanship, JCR consulting, and Java development
