Oliver Zeigermann <[EMAIL PROTECTED]> writes: > 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 > and much more. Remove this or explain, what else is available. > 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. +1 > 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. For many reports it should be obvious, if they are still valid. > 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. > > 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 > > 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 > > Other: > - src/contrib will be removed > - src/examples will be removed > - src/admin will be removed > - src/tablib will be removed > > ACL: > - SecurityImplAllGrant will be removed, as it is no longer supported > > JDK SUPPORT > ------------ > > 1.3 required, 1.4 recommended +1 Which version of ant is required for building? 1.5? > 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. > > > 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 There should be some kind release in the end of January. Lets decide in January, if we call it alpha or beta. > 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. The naming scheme is not in sync with the description in RELEASE-INFO. Changing the logging in 2.1 will be a change to the API. RELEASE-INFO says, that API changes require a new major number. Note that there are already tags 2_0_0 and 2_0_1 in CVS. > - 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. +1 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
