| | 1 | {{{ |
| | 2 | #!rst |
| | 3 | |
| | 4 | Mapserver 4.6.0 was released on June 14, 2005. The release plan is still available below for reference. |
| | 5 | |
| | 6 | --- |
| | 7 | |
| | 8 | This 4.6 release plan was agreed between the developers. Information below may still change slightly as the release progresses. |
| | 9 | |
| | 10 | Planned Dates |
| | 11 | ------------- |
| | 12 | |
| | 13 | 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: |
| | 14 | |
| | 15 | * Feature freeze - April 20th, 2005 |
| | 16 | * 4.6.0-beta1 - April 25th (done on 2005-04-26) |
| | 17 | * 4.6.0-beta2 - May 9th (done on 2005-05-11) |
| | 18 | * 4.6.0-beta3 - May 23rd (done on 2005-05-27) |
| | 19 | * 4.6.0-rc1 - May 30th (done on 2005-06-09) |
| | 20 | * 4.6.0 (final) - June 6th (done on 2005-06-14) |
| | 21 | |
| | 22 | CVS Tags/Branches? |
| | 23 | ------------------ |
| | 24 | |
| | 25 | * The main trunk (HEAD) in CVS is currently the 4.5 development version that we plan to release as 4.6 |
| | 26 | * The stable CVS branch for this release will be called "branch-4-6" (not created yet). |
| | 27 | * Current proposed date for creating "branch-4-6" is the date of the 4.6.0 release (around June 6th) |
| | 28 | * If post-4.6 developments require earlier branching then please bring up your request for branching on the -dev list. |
| | 29 | * 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... |
| | 30 | |
| | 31 | Bugzilla Conventions |
| | 32 | -------------------- |
| | 33 | |
| | 34 | 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: |
| | 35 | |
| | 36 | * Bugs to be addressed for this release must have their target milestone set to "4.6 release" |
| | 37 | * 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 |
| | 38 | * The target milestone on a bug should be set by the developers (bug owners) and not by the users (reporters). |
| | 39 | |
| | 40 | Other good practices when dealing with bugs: |
| | 41 | |
| | 42 | * 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). |
| | 43 | * Please mark bugs ASSIGNED as soon as you start working on them |
| | 44 | * 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. |
| | 45 | * When committing to CVS, please include the bug number in your CVS change log comment. |
| | 46 | * 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. |
| | 47 | |
| | 48 | 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 |
| | 49 | |
| | 50 | |
| | 51 | Open Tasks |
| | 52 | ---------- |
| | 53 | |
| | 54 | * Documentation updates - Coordinate with all documentation contributors to bring all documents up to date for the release |
| | 55 | * Resp: Kari |
| | 56 | * Bug #: |
| | 57 | * Status: |
| | 58 | |
| | 59 | |
| | 60 | Completed Tasks |
| | 61 | --------------- |
| | 62 | |
| | 63 | Once completed, the tasks above should be moved down here. |
| | 64 | |
| | 65 | * MapServer performance issue - Z and M cause performance lost |
| | 66 | * Resp: Julien |
| | 67 | * Bug #: 1244 |
| | 68 | * Status: Completed |
| | 69 | |
| | 70 | * MapServer performance issue - Label outline performance issue |
| | 71 | * Resp: Steve / Julien |
| | 72 | * Bug #: 1243 |
| | 73 | * Status: Set to Future, See bug for details |
| | 74 | |
| | 75 | * Layer tolerance - Tolerance default value should be based on the layer type |
| | 76 | * Resp: Steve / Julien |
| | 77 | * Bug #: 1103 |
| | 78 | * Status: Completed |
| | 79 | |
| | 80 | * GEOS Integration |
| | 81 | * Resp: Steve |
| | 82 | * Bug #: 770 |
| | 83 | * Status: done |
| | 84 | |
| | 85 | * Support for GML Profiles |
| | 86 | * Resp: Steve |
| | 87 | * Bug #: 950 |
| | 88 | * Status: done |
| | 89 | |
| | 90 | }}} |
