{{{
#!rst

Mapserver 4.6.0 was released on June 14, 2005. The release plan is still available below for reference.

---

This 4.6 release plan was agreed between the developers. Information below may still change slightly as the release progresses.

Planned Dates
-------------

Based on our experience with the other 4.x releases, we will plan for 3 betas over a 6 weeks period after the code freeze. This would lead us to a final release in early June:

* Feature freeze - April 20th, 2005
* 4.6.0-beta1 - April 25th (done on 2005-04-26)
* 4.6.0-beta2 - May 9th (done on 2005-05-11)
* 4.6.0-beta3 - May 23rd (done on 2005-05-27)
* 4.6.0-rc1 - May 30th (done on 2005-06-09)
* 4.6.0 (final) - June 6th (done on 2005-06-14)

CVS Tags/Branches?
------------------

* The main trunk (HEAD) in CVS is currently the 4.5 development version that we plan to release as 4.6
* The stable CVS branch for this release will be called "branch-4-6" (not created yet).
* Current proposed date for creating "branch-4-6" is the date of the 4.6.0 release (around June 6th)
* If post-4.6 developments require earlier branching then please bring up your request for branching on the -dev list.
* The betas will be tagged in CVS as "rel-4-6-0-beta1", "rel-4-6-0-beta2", ... and the releases as "rel-4-6-0", "rel-4-6-1", etc... 

Bugzilla Conventions
--------------------

In order to facilitate querying the bugzilla database for bugs that still need to be addressed for this release, we try to stick to the following conventions:

* Bugs to be addressed for this release must have their target milestone set to "4.6 release"
* Bugs/Enhancements? that can't make it in this release but that we may want to address at a later time should be marked with the "FUTURE" target milestone with a comment explaining that the bug is postponed and if possible a quick analysis
* The target milestone on a bug should be set by the developers (bug owners) and not by the users (reporters). 

Other good practices when dealing with bugs:

* Please file bugs for any non-trivial bugfix or change to the software. This is so that we keep a trace for future reference of all bugfixes and changes that were made (why and how).
* Please mark bugs ASSIGNED as soon as you start working on them
* Please when marking a bug fixed include a comment describing the fix, the version of the software in which it was done, and any other relevant information. This will just make our lives easier in a few months/years when questions come up about this issue.
* When committing to CVS, please include the bug number in your CVS change log comment.
* Keep documentation in mind when fixing/changing things: if you cannot update the documentation yourself then please create a documentation bug describing the new feature/change and which document(s) should be updated. 

The following query returns all currently open bugs that are tagged with the "4.6 release" target milestone: http://mapserver.gis.umn.edu/bugs/buglist.cgi?target_milestone=4.6+release&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED


Open Tasks
----------

* Documentation updates - Coordinate with all documentation contributors to bring all documents up to date for the release
   * Resp: Kari
   * Bug #:
   * Status:


Completed Tasks
---------------

Once completed, the tasks above should be moved down here.
 
* MapServer performance issue - Z and M cause performance lost
   * Resp: Julien
   * Bug #: 1244
   * Status: Completed

* MapServer performance issue - Label outline performance issue
   * Resp: Steve / Julien
   * Bug #: 1243
   * Status: Set to Future, See bug for details

* Layer tolerance - Tolerance default value should be based on the layer type
   * Resp: Steve / Julien
   * Bug #: 1103
   * Status: Completed

* GEOS Integration
   * Resp: Steve
   * Bug #: 770
   * Status: done

* Support for GML Profiles
   * Resp: Steve
   * Bug #: 950
   * Status: done

}}}