I was wondering about the message we're sending to the user community by
certifying a milestone release. (I think its the right thing to do by
the way). I believe there is some pent up expectation that
certification means go for production but my opinion is that certifying
a milestone is really more of a tech-preview. What are the thoughts on
communicating what this means to the user community in terms of what
should they be doing with Geronimo with regard to development,
production, etc?
Also, personally I'd like to make some statement about when we would be
expecting to deliver 1.0 so the user base can set their expectations
appropriately.
I think something like M5-Tech Preview contains all J2EE 1.4
functionality as well as new technology that is not finished such as the
console, usability improvements, etc. With a target date for V1.0
around the end of October 2005.
Thoughts?
Matt
Bruce Snyder wrote:
On 9/12/05, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Sorry to put this as a vote thread, but there was already a lingering
thread on this and we never seemed to get to the core issue. We
discussed worries about the additional effort, but I'm convinced that
no one wants to issue a M5 w/o passing the testsuite, so in a sense,
the question is somewhat moot.
M4 passed the automated tests, and M5 will. And with M5, we seem to
have no problems with the untestable assertions.
Shall we declare this our J2EE 1.4 certified release?
Yes from me :)
+1 on the condition that both Jetty and Tomcat can pass the TCK.
Bruce
