updates

git-svn-id: http://mantisbt.svn.sourceforge.net/svnroot/mantisbt/trunk@631 f5dc347c-c33d-0410-90a0-b07cc1902cb9

roadmap.php3

@@ -3,52 +3,47 @@
 <span class="page_title">Roadmap</span>
 <hr size=1 noshade width="100%">
 <p>
-This is the Mantis feature roadmap.  It lists most of the currently planned features and details the schedule for release.  These are not hard deadlines and are subject to change.  Please feel free to suggest features, contribute, or comment.
+This is the Mantis feature roadmap.  It lists most of the currently planned features and details the schedule for release.  These are not hard deadlines and are subject to change.  Occasionally things will get out of date or out of order as schedules are wont to do.  Please feel free to suggest features, contribute, or comment.
 <p>
 
-<span class="section">0.16.0</span>
-<ul>
-	<li>Rework HTML posting
-	<li>Create file hierarchy for docs, config, etc.
-	<li>Configuration Documentation - list basic ways in which Mantis can be customized; quickstart guide for customization needs
-	<li>List modified files for each release - let users know what exactly has changed in each upgrade
-	<li>Fleshed out test settings script - let admins easily diagnose if settings are correct
-	<li>Print friendly form - use fewer table elements; more like email; also for summary and view all bugs
-	<li>Break up config_inc.php into commonly modified items to avoid upgrade headaches
-	<li>Lockdown security permissions
-	<li>Allow for project/bug_id email links to work properly.
-</ul>
 <span class="section">0.17.0</span>
 <ul>
+	<li>Allow for project/bug_id email links to work properly.
 	<li>Have user settings per project - email preferences should be configurable on a per project basis
-	<li>Vote support - users may add a 'me too' vote to assist in showing which bugs are most common
-	<li>ETA support -
-	<li>Priority support -
-	<li>Projection support -
-	<li>Logged in Summary ( bugs reported, assigned, new in last week, high priority, open long time, etc. )
-	<li>Show number of concurrent users - like Freshmeat.net
+	<li>Lockdown security permissions
+	<li>Break up config_inc.php into commonly modified items to avoid upgrade headaches
+	<li>Break up Mantis into subdirectories (docs, config, images, etc.)
 </ul>
+
 <span class="section">0.18.0</span>
 <ul>
+	<li>Show number of concurrent users - like Freshmeat.net
+	<li>Rework HTML posting
+	<li>Create file hierarchy for docs, config, etc.
 	<li>Bug Search (Advanced) - fleshed out search with multiple options (search in bugnotes, categories, etc)
 	<li>Multiple sort keys (?) - let people select more than one ordering for searches (complicated interface)
 	<li>Monitor bug (for anyone) - users can click a 'Monitor Bug' option to let them be included in the email notifications
-	<li>Unread/Read bugs indicator - developers and above will see a icon indicating an unread bug
+	<li>Bug history logging
+	<li>Bug relationship fields (Duplicate of, Depends on, Parent of, etc.)
 </ul>
 
 <span class="section">0.19.0</span>
 <ul>
+	<li>List modified files for each release - let users know what exactly has changed in each upgrade
 	<li>Mantis Logo - about time, right?
 	<li>Little glyphs and graphics for site - asthetic niceties
-	<li>Break up Mantis into subdirectories (docs, config, images, etc.)
+	<li>Vote support - users may add a 'me too' vote to assist in showing which bugs are most common
+	<li>ETA support
+	<li>Priority support
+	<li>Projection support
+	<li>Move configuration variables into the database
 </ul>
 
 <span class="section">1.x.x</span>
 <ul>
 	<li>Rework bug formatting - adjust to any changes that need to be made (especially in simpler vs. advanced mode)
 	<li>Let administrators customize additional information fields for bug report details (CPU, RAM, etc) - using a simple interface, let the admin add fields to the bug report. this will make the entry of these fields more explicit
 	<li>Abstract account management - make it easier for other packages to be integrated
-	<li>Related to bug field - similar to duplicate ID; maybe lead to a dependency graph (are these worth it?)
 </ul>
 <span class="section">2.x.x</span>
 <ul>