Janne did sound a tad cranky. I think he was simply offering advice
similar to what my boss used to say when I'd bring him a problem.
He would say, "don't bring me a monkey without bringing me the cage
too."
That, too.
I'd echo most of what he said. The goals of 2.8 were to have an
Apache-licensed version, with very few API changes and a modest set
of enhancements. This puts us on track to do the real Apache
release, with the org.apache structure, for 3.0.
BTW, Ohloh says that our code base has not been growing at all during
1H of this year. Most of the effort has gone into apachifying
everything, which is why we have little or no new features for 2.8
looking into tools like JarJarDiff that help spotlight API changes.
Also, quick summaries of changes for developers and deployers would
be good. The Stripes folks do this quite well, and I'm planning on
copying their format.
We do have the ReleaseNotes, but they're probably not that
descriptive right now.
(I'd very much like to start working on the new API library as well.)
But anyway, to return to my first question: can we start the alpha/
beta cycle of 2.8? So far I seem to be the only one who thinks so...
/Janne
