> 0 issues! Congrats everyone. 2.9 was quite a beast. > > So looks like we should get a few things in order. > > 1. Anyone dying to be release manager? I think I could do it, but I'm > kind of pressed for time ... > > 2. Lets start crawling all over this release - bugs/javadoc/packaging etc. > > 3. In regards to that - I'd like to suggest that we don't do the release > branch early for 2.9. I know we normally make the release > branch so that further dev can continue on trunk. In this case I > don't think that is wise. I propose that we lock down trunk for a > while, to force people to concentrate on *this* release. Otherwise we > divide our limited forces into two - those working on release, and those > working on trunk and beyond. We can kind of enforce this by making the > release branch last minute I think.
I think 3.0 is a little bit special: We move to Java 1.5, so in my opinion, we should not only remove deprecations, but also add Generics and remove StringBuffer and so on. I have some "patches" for that available, e.g. the casting currently needed for the Attributes API can be more elegantly solved by using generics (something like "T addAttribute(Class<T extends Attribute>)"). If we do not add generics to the public API in 3.0, we have to wait one major release longer to add them. To get the 3.0 release shortly after 2.9, we should branch now, that the generics commits could be done early. I would also help to do this (at least for the parts I was working on the last time). > 4. I suggest we offer an early release candidate type build (very soon) > - nothing official, nothing signed - just something easier for our user > community to test with if they are not very familiar with building a > release off of trunk. +1 Start the release process! Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
