Hey all,
I haven't seen a roadmap for a 2.2 release (slide 2.2
server/wevdav/stores, not the client). 

Here are some items that, to me, look like good goals for a 2.2 release
based on the bugzilla reports:

*identify and correct/educate unable-to-post-2g file problem (whether
file-system-limitation or Slide problem)
http://issues.apache.org/bugzilla/show_bug.cgi?id=38353
*similar putting-large-files problem
http://issues.apache.org/bugzilla/show_bug.cgi?id=28894

*TxXmlFileDecriptor Implementation vs Abstractfiledescriptor -
consistent API http://issues.apache.org/bugzilla/show_bug.cgi?id=36689

*Small NPE issue fix with patch
http://issues.apache.org/bugzilla/show_bug.cgi?id=36551

*Lucene/DASL sorting improvement
http://issues.apache.org/bugzilla/show_bug.cgi?id=36045

*path's too long in windows-based FS stores - what should the behavior
be http://issues.apache.org/bugzilla/show_bug.cgi?id=35608

*httpclient 3.0 support
http://issues.apache.org/bugzilla/show_bug.cgi?id=35213

*Accent/url encode/decode problem
http://issues.apache.org/bugzilla/show_bug.cgi?id=34679
*another encode/decode patch
http://issues.apache.org/bugzilla/show_bug.cgi?id=31265

*delete returns 'true' even when fails
http://issues.apache.org/bugzilla/show_bug.cgi?id=33565
*move returns 'true' even when fails
http://issues.apache.org/bugzilla/show_bug.cgi?id=33498

Also, mailing thread 'Performance & Version 2.2' started by Meltem - I
couldn't see the test results that they posted, but if that could become
available and a measured benchmark for improvements.  Even if no
performance gains are made on a 2.2 release, at least look at adding a
performance test-suite (if one doesn't already exist).

This is for a 2.2 release, not a 3.0 refactor that may also be in the
works. Hopefully someone who is more in-tune with the slide system can
remove any that do not make sense, or add new ones that make sense?
Otherwise, anyone looking for direction, at least this is a start!

P.s. since these are more 'bugfixes' for 2.2 rather than an actual
roadmap, leaving it within the dev mailing list opposed to the wiki.

-D





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to