> -----Original Message----- > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 27, 2003 13:16 > To: Slide Developers Mailing List > Subject: VOTE: Slide 2.0 release > > > Hi, folks! Seems to be time for the vote upon the 2.0 release! > > 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
+1 A note on DeltaV: it should be clear, that Slide 2.0 will *not* support the so called "advanced features" of the spec, i.e. the features "merge", "basline", "activity" and "versioned collection" are postponed to 2.x (x>0). > and much more. > > SHOWSTOPPERS > ------------ > - Authentication wrapper must be fixed (maybe done already :) > - Docs must be updated, Web as well as internal (CVS) > - At least all *functional* tests should pass or only fail > for known and > documented reasons (in release notes) +1 > > BUGZILLA > -------- > > Bugzilla shall be the primary place for bug reports and associated > patches. As the status of quite some reports is unclear all > reports not > yet assigned will be deleted and reporters are kindly asked to > re-submit reports still valid. This is supposed to make the usage of > bugzilla more attractive. +1 > CLIENT > ------ > > The client should be moved to dedicated area with a dedicated build > script. > +1 > ACL > --- > > The only supported ACL-draft will be the current version 12. No other > ACL policies will be supported. +1 > 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. +1 Of course, the CVS attics should not be removed :) > Kernel (src/share section): > - org.apache.slide.store.StandardStore will be replaced by > ExtendedStore > along with this the following classes will be deleted from package > org.apache.slide.util: > - AbstractObjectCache > - HashMap > - HashMapObjectCache > - Iterator +1 I'd go for *not* deleting but marking StandardStore as deprecated in a first step in order to allow store implementations existing somewhere outside Slide to move to ExtendedStore. > Stores: > - Package org.apache.slide.store.impl.rdbms will be removed completely > and replaced by the merged version in the proposals section > - Package slidestore will be removed completely. Classes from package > slidestore.file needed by tx file store will be moved to > org.apache.slide.store and will finally vanish with BIND > implementation: > - AbstractUriProperties > - UriProperties +1 > Other: > - src/contrib will be removed > - src/examples will be removed > - src/admin will be removed > - src/tablib will be removed > +/-0 Not sure about this. If needed, probably can be reanimated in a later release. > ACL: > - SecurityImplAllGrant will be removed, as it is no longer supported +1 > JDK SUPPORT > ------------ > > 1.3 required, 1.4 recommended > +1 > LOGGING > ------- > > Logging API will be augmented by a method allowing for both > message and > throwable in one call. A general redesign of logging is deferred to > later releases. > +1 > NEW FEATURES > ------------ > > All newly discussed features go into 2.1 or even later > releases, no new > features go into 2.0. > +1 > BINARY RELEASE > -------------- > > - WAR > - Tomcat bundle > - Separate Client binary release > +1 > 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 > > > RELEASE PROCEDURE > ----------------- > > - Releases will be done as described in RELEASE-INFO in the CVS. > > - As soon as there is a definite feature freeze a release > branch called > SLIDE_2_0 will be created. After that all fixes must be > applied to this > branch. New features will be added to the HEAD. > > - As soon as the release goes out, release notes must be checked into > the CVS. They should contain general info, fixed bugs, enhancements, > known issues, etc. Regards, Peter
