I thought of a couple more:
. Add copyright statement to the top of all files. I haven't been
doing a good job of remembering to do that/enforcing it in new checkins.
We'll want to sweep through and do it before the release.
. Address upgrade scenarios. I'm not sure whether this one is
something we *need* to do or not, but it would be nice if we could
automatically migrate from the morass of <appSettings /> stuff that FlexWiki
1.8 uses to the flexwiki.config file, maintaining as much as we can.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig
Andera
Sent: Tuesday, August 07, 2007 9:19 AM
To: 'FlexWiki Users Mailing List'
Subject: [Flexwiki-users] Shipping FlexWiki 2.0 - Proposed Feature List
Now that performance looks like it's more or less where it needs to be, I
want to get consensus on what constitutes FlexWiki 2.0 RC1. Here's the list
of things I can think of that need to be fixed or added:
. Address outstanding SQL Server bug reported here.
. Address outstanding search page bug reported here.
. Complete new stylesheet work.
. Complete or partially complete XHTML compliance work.
. Add administration page for working with new cache (clear items,
view cache, etc.)
. Add administration page for working with new configuration file
format (reload config, edit config file online, etc.)
That's a fairly short list, which is very good! Can anyone think of anything
else that I'm forgetting that should go into 2.0 RC1?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
