On Dec 5, 2006, at 10:21 AM, Matt Hogstrom wrote:
> Should we use M<N>
> ------------------
> Jason posted in another thread about how M<n> (I assume you were
> referring to Milestones) might be confusing for post 1.0 releases.
> I don't think its confusing as it represents a simple point in time
> reference of a work in progress but not a full implementation (I
> think that build would more appropriately be a beta). Alpha
> release might be appropriate but I'm good with milestone. Other
> thoughts?
We have a history of using M1 syntax for releases and see no reason
to change that.
> Content
> -------
> At this point M1 would contain:
>
> Java 1.5 as the base JDK
> Tomcat and Jetty for Servlet 2.5, JSP 2.1 and Debugging support.
> JTA 1.1
> JSF (depending on where the MyFaces folks are at)
> JSTL (I think Joe was working on this)
>
> Once we get this together and we can run Daytrader 2.0-SNAPSHOT on
> it I think we have a content ready milestone.
We already have JPA but it is so cool we should mention it again :)
> Timeline
> --------
> This is less important than the content. I suggested 12/22 since
> its the Friday before the Christmas holiday. Personally it would
> feel good to know we packaged up something and finished it this
> year towards 2.0. There is a lot of small stuff we already have
> thats almost done. We've been discussing release early and often
> so the date is more of an artificial stake in the sand. If we
> don't get the work done then we don't ship. It largely depends on
> completing what goes into M1 rather than the date.
+1 Lets get'er done
-dain
|