Hi, folks! Seems to be time for the vote upon the 2.0 release!
This should be "the 2.0 release plan". Of course, each release (alpha, beta, whatever) needs a separate vote. A must-read (IMHO) for a release manager is Robert's great guidelines for the Jakarta-Commons project:
http://jakarta.apache.org/commons/releases/
Not all applies to Slide, but most.
Furthermore, I think you should add the release plan to CVS (there is already a release plan for 1.0). There, the plan can evolve in a controlled manner, until all committers are okay with it.
It is important (at least for me) that all committers regarding themselves as active (of course including new committer Martin Holz) give a vote here!
Of course, every topic gets my +1 :)
GENERAL -------
Slide 2.0 will provide a stable content repository for content management systems / frameworks and other purposes, featuring: * Full WebDAV Support * DeltaV WebDAV Versioning Support * Support for a variety of backend systems for storing the content including different databases and file system storage * Transactions and Locking for data integrity * Flexible control over permissions at a per file level via support for WebDAV ACL * Simple installation on any server supporting Servlet 2.3 and .war deployment * Sample 'ready-to-run' binary distribution including Tomcat 4.1 * A fully featured WebDAV client library and command line client
and much more.
I'd get rid of the "and much more" ;-)
[snip]
STUFF TO BE REMOVED *NOW* -------------------------
All classes that do not go into the 2.0 release will be deleted using "CVS remove" directly after the vote. Attic directory will be removed as well.
I hope you're referring to the 'attic' directory that you created, and not to the CVS Attics (which should never ever be removed).
Kernel (src/share section): - org.apache.slide.store.StandardStore will be replaced by ExtendedStore
So is there a need to actually *delete* StandardStore? Why not just deprecate it and point to ExtendedStore in the doc comment?
OTOH, if you really want to remove StandardStore, why not replace it with ExtendedStore (keeping the name). Doesn't make much sense to have something "extended" if there's nothing basic it extends.
[snip]
RELEASE PLAN ---------------------
- There will be no milestone releases - Slide 2.0beta release: 3rd-4th week of Janury 2004 - Slide 2.0final release: 3rd-4th week of February 2004
You are aware that Slide has been using a different versioning scheme than what you're proposing here?
The versioning scheme is the same as used by HTTPD and Tomcat. Every release, regardless of whether it's considered stable or alpha or whatever, get's a version number of the form major.minor.x, where x is a number starting at 0 and incremented for every release. Then, 1-2 weeks after the release, a vote is casted to give the release a stability rating (alpha | beta | stable). Only after that is the release officially announced.
That's why the first stable release of Slide has the version 1.0.16.
So, just be aware that you'd be changing this rule with the proposed versioning. I like the HTTPD versioning scheme, personally, but my vote doesn't count much these days ;-)
-chris
PS: the energy you're putting into all this is impressive and much appreciated, I really hope my constant bickering isn't creating the wrong impression :-P
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
