Changes between Initial Version and Version 1 of 44ReleasePlan


Ignore:
Timestamp:
Dec 3, 2008, 11:31:47 AM (15 years ago)
Author:
hobu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • 44ReleasePlan

    v1 v1  
     1{{{
     2#!html
     3
     4<p>
     5This 4.4 release plan has been agreed between the developers. However the information below may still change slightly as the release progresses.
     6<p>
     7<H3>Planned Dates</H3>
     8
     9<p>
     10Based on our experience with 4.2.0, we will plan for 3 betas over a 6 weeks period after the code freeze. This would lead us to a final release around endof November:
     11<p>
     12<UL>
     13
     14<li> Feature/Code<a href="wiki.pl?action=edit&id=ReleasePlan44/Code">?</a> freeze - October 17th (done)
     15<li> 4.4.0-beta1 - October 21st
     16<li> 4.4.0-beta2 - November 3rd
     17<li> 4.4.0-beta3 - November 15th (done on Nov 21st)
     18<li> 4.4.0 (final) - November 29th (done)
     19</UL>
     20<p>
     21<H3>CVS Tags/Branches<a href="wiki.pl?action=edit&id=ReleasePlan44/Branches">?</a></H3>
     22
     23<p>
     24<UL>
     25<li> The main trunk (HEAD) in CVS is currently the 4.3 development version that we plan to release as 4.4
     26<li> The stable CVS branch for this release will be called "branch-4-3" (not created yet).
     27<li> Current proposed date for creating "branch-4-3" is the date of the 4.4.0 release (around Nov 29th)
     28<li> If post-4.4 developments require earlier branching then please bring up your request for branching on the -dev list.
     29<li> The betas will be tagged in CVS as "rel-4-4-0-beta1", "rel-4-4-0-beta2", ... and the releases as "rel-4-4-0", "rel-4-4-1", etc...
     30</UL>
     31<p>
     32<H3>Bugzilla Conventions</H3>
     33
     34<p>
     35In 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:
     36<p>
     37<UL>
     38<li> Bugs to be addressed for this release <b>must</b> have their target milestone set to "4.4 release"
     39<li> Bugs/Enhancements<a href="wiki.pl?action=edit&id=ReleasePlan44/Enhancements">?</a> 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
     40<li> The target milestone on a bug should be set by the developers (bug owners) and not by the users (reporters).
     41
     42</UL>
     43<p>
     44Other good practices when dealing with bugs:
     45<p>
     46<UL>
     47<li> Please file bugs for <b>any</b> 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).
     48<li> Please mark bugs ASSIGNED as soon as you start working on them
     49<li> 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.
     50<li> When committing to CVS, please include the bug number in your CVS change log comment.
     51<li> 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.
     52
     53</UL>
     54<p>
     55The following query returns all currently open bugs that are tagged with the "4.4 release" target milestone:
     56<a href="http://mapserver.gis.umn.edu/bugs/buglist.cgi?target_milestone=4.4+release&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">http://mapserver.gis.umn.edu/bugs/buglist.cgi?target_milestone=4.4+release&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED</a>
     57<p>
     58<H3>Open Tasks</H3>
     59
     60<p>
     61<UL>
     62<li> Documentation updates - Coordinate with all documentation contributors to bring all documents up to date for the release
     63<UL>
     64
     65<li> Resp: Kari
     66<li> Bug #:
     67<li> Status:
     68</UL>
     69</UL>
     70<p>
     71<UL>
     72<li> Connection Pooling - Expose to SWIG <a href="wiki.pl?MapScript">MapScript</a>
     73<UL>
     74<li> Resp: Sean
     75
     76<li> Bug #:
     77<li> Status:
     78</UL>
     79</UL>
     80<p>
     81<p>
     82<UL>
     83<li> Dump data from imageObj to filehandle (swig mapscript)
     84<UL>
     85<li> Resp: Sean
     86<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=941">[#941]</a>
     87
     88<li> Status: core code in place, soliciting typemap contributions from scripting language users.
     89</UL>
     90</UL>
     91<p>
     92<UL>
     93<li>
     94<UL>
     95<li> Resp:
     96<li> Bug #:
     97<li> Status:
     98</UL>
     99</UL>
     100<p>
     101
     102<H3>Completed Tasks</H3>
     103
     104<p>
     105Once completed, the tasks above should be moved down here.
     106<p>
     107<UL>
     108<li> Connection Pooling - SDE
     109<UL>
     110<li> Resp: Howard
     111<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=942">[#942]</a>
     112<li> Status:  Connection pooling for SDE has been implemented using the new connection pooling API, and under my testing appears to be working well.  One change that was made is that SDE versions are now specified in the DATA definition of the layer rather than the CONNECTION.  The only place that I know of documentation showing how to use SDE versions in <a href="wiki.pl?MapServer">MapServer</a> was in the wiki, and I don't think the change will be that disruptive, as I think the number of users of this feature is small.  If people do not have versions specified anywhere, SDE.DEFAULT is used as before with (hopefully) no ill effects.  Thread locking on the SDE connection has been applied using SDE's locking facility.  See the source code for more information.
     113
     114</UL>
     115</UL>
     116<p>
     117<UL>
     118<li> <a href="wiki.pl?FastCGI">FastCGI</a>
     119<UL>
     120<li> Resp: Frank
     121<li> Bug #:
     122<li> Status: complete, only tested with WMS so far.
     123</UL>
     124</UL>
     125<p>
     126
     127<UL>
     128<li> Connection Pooling - core and <a href="wiki.pl?PostGIS">PostGIS</a>
     129<UL>
     130<li> Resp: Frank
     131<li> Bug #:
     132<li> Status: apparently complete for 4.4, multi-threadsafe version likely left to post 4.4.
     133</UL>
     134</UL>
     135<p>
     136<UL>
     137<li> Dynamic class creation (swig mapscript)
     138
     139<UL>
     140<li> Resp: Sean
     141<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=939">[#939]</a>
     142<li> Status: Complete
     143</UL>
     144</UL>
     145<p>
     146<UL>
     147<li> writeQuery/saveQuery (swig mapscript)
     148<UL>
     149<li> Resp: Sean
     150
     151<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=921">[#921]</a>
     152<li> Status: done, awaiting confirmation from reporter
     153</UL>
     154</UL>
     155<p>
     156<UL>
     157<li> Internationalization (iconv)
     158<UL>
     159<li> Resp: Julien/Daniel<a href="wiki.pl?action=edit&id=ReleasePlan44/Daniel">?</a>
     160
     161<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=858">[#858]</a>, <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=909">[#909]</a>, <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1017">[#1017]</a>, <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=911">[#911]</a>
     162<li> Status: Implementation complete. Doc pending in bug <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=890">[#890]</a>.
     163</UL>
     164</UL>
     165<p>
     166
     167<UL>
     168<li> WCS Server
     169<UL>
     170<li> Resp: Steve
     171<li> Bug #:
     172<li> Status: Done.
     173</UL>
     174</UL>
     175<p>
     176<UL>
     177<li> Time support in WMS
     178<UL>
     179
     180<li> Resp: Assefa
     181<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=872">[#872]</a>
     182<li> Status: Implementation done. Docs (HOWTO) live.
     183</UL>
     184</UL>
     185<p>
     186<UL>
     187<li> Connection Pooling - Oracle
     188<UL>
     189<li> Resp: Fernando
     190
     191<li> Bug #:
     192<li> Status: Done in beta2.
     193</UL>
     194</UL>
     195<p>
     196<UL>
     197<li> Map Context support in mapserver cgi
     198<UL>
     199<li> Resp: Assefa
     200<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=946">[#946]</a>
     201
     202<li> Status: code done. QA done. Docs updated.
     203</UL>
     204</UL>
     205<p>
     206<UL>
     207<li> Support for Z shapefiles
     208<UL>
     209<li> Resp: Assefa
     210<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=869">[#869]</a>, <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=870">[#870]</a>, <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=871">[#871]</a>
     211
     212<li> Status: php mapscript functions are done(870). Swig version done (871).
     213</UL>
     214</UL>
     215<p>
     216<UL>
     217<li> Try to cleanup the PHP/regex mess
     218<UL>
     219<li> Resp: Daniel
     220<li> Bug #: <a href="http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=520">[#520]</a>
     221<li> Status:
     222
     223</UL>
     224</UL>
     225<p>
     226<UL>
     227<li> Review open bugs and try to get all critical ones fixed before code freeze, or at least flagged with "4.4-release" target milestone.
     228<UL>
     229<li> Resp: All developers
     230<li> Bug #: n/a
     231<li> Status:
     232</UL>
     233</UL>
     234<p>
     235}}}