Yes, I agree that a road map is a good idea. I also think Tapestry should take a page from the Eclipse bible, on many fronts.
Efforts on the Eclipse platform always start with a plan: http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html (not a huge document, but if one is pressed for time one can get the gist of the intent of the plan by reading the early section that starts with "Plans do not materialize out of nowhere, nor are they entirely static.") One thing that I find really neat is that those folks identify the important themes for each major release, identify those themes in the plan and relate most of the rest of items of the plan to these themes. Some examples (from the present draft plan and from other, older, plans I've seen) Design for Extensibility Enterprise Ready Simple to Use Build to Last Eclipse is a big project and there are many many themes they observe, but they do pick a finite list for each major effort and partially base what plan items are in or out based on the target themes. BTW. Build To Last is a great theme and one that I think those folks have mastered. Think about the amount of code in Eclipse and they we able to put of Eclipse 3.1 with a very short list of breaking changes. >From 3.0 to 3.1 there are sixteen to be exact. http://help.eclipse.org/help31/topic/org.eclipse.platform.doc.isv/porting/3.1/incompatibilities.html Not that there weren't huge changes in 3.1 but they were able to do the majority without breaking clients. Gamma on a bunch of stuff including Build To Last: http://www.artima.com/lejava/articles/designprinciples.html And I think that Build To Last is applicable whether or not the next big version of Tapestry is a world changer or not. Geoff On 11/12/05, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > Howard Lewis Ship wrote: > > There's no such thing as perfect; I'm pretty satisfied with the code > > today, even if there will be a need for a 4.0.1 bug fix. And I have > > some great plans for 4.1 (that are a lot less disruptive than 3.0 -> > > 4.0). > > > Let's share them! A nice 'Roadmap' on the main Tapestry page can get > people excited about the project. A lot of times I go looking for open > source frameworks / libraries, and their 'roadmap' page (along with its > documentation) gives a good impression. At least people know where is > this going, and how great plans are. > > -- > Ing. Leonardo Quijano Vincenzi > Director Técnico > DTQ Software > > -- > > Howard M. Lewis Ship > > Independent J2EE / Open-Source Java Consultant > > Creator, Jakarta Tapestry > > Creator, Jakarta HiveMind > > > > Professional Tapestry training, mentoring, support > > and project work. http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Announcement Feed: http://www.jroller.com/rss/glongman?catname=/Announcements Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
