Changes between Version 1 and Version 2 of TinyOWSModGeocacheIntegration
- Timestamp:
- Aug 5, 2011, 7:13:13 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TinyOWSModGeocacheIntegration
v1 v2 11 11 12 12 == Sub-project names == 13 14 * How do we refer to the two sub-projects once merged? Do we call them sub-projects? Modules? Components? 15 * If we want the whole thing to be promoted as a "MapServer Suite" (or stack, or ....) then we need clear names for each component 16 * MapServer core needs a name (or do we just call it "MapServer core" ... or CGI? 17 * MapSript? 18 * RFC 70 says nothing about the way the preferred name for TinyOWS after the merge 19 * RFC 71: “Mod-Geocache” as a name is a poor choice, and should be changed during the integration with MapServer. The author has no predefined idea as to what the solution should be named, ideas will be greatly appreciated. 13 20 14 21 == License == 15 22 16 * RFC70: TinyOWS already use MIT licence, as MapServer does. Copyright holders (Barbara Philippot and Olivier Courtin) should be kept on existing TinyOWS files. 17 * RFC71: The apache licence of mod-geocache will be switched to the same licence as MapServer. 23 * MIT in all cases: 24 * RFC 70: TinyOWS already use MIT licence, as MapServer does. Copyright holders (Barbara Philippot and Olivier Courtin) should be kept on existing TinyOWS files. 25 * RFC 71: The apache licence of mod-geocache will be switched to the same licence as MapServer. 18 26 19 27 == Release planning / scheduling == … … 22 30 23 31 * Release numbering? 24 * MapServer 6.x, TinyOWS 1.x, mod_geocache 0.4 ... confusing if we want to appear as a unified project... and then which version number do we g ove to the complete suite?32 * MapServer 6.x, TinyOWS 1.x, mod_geocache 0.4 ... confusing if we want to appear as a unified project... and then which version number do we give to the complete suite when we release as a whole? 25 33 * Adopt a common release numbering scheme? e.g. Ubuntu-style based on year.month? Would allow intermediate releases by component, while having consistent release numbers between all components ... e.g. MapServer suite with all components initially released as 11.08 (august 2011), next major release of MapServer core planned for early 2012, but in the meantime sub-projects can be released as 11.10, 11.11, etc... and next full suite release (including MapServer core) could be around February as v12.2? 26 34 * Other options? … … 29 37 == Build system integration == 30 38 31 Single build system or multiple/separate ones? It seems that we need a mix of both... 39 Single build system or multiple/separate ones? It seems that we need a mix of both... Daniel has some ideas 32 40 33 41 == Source and binary packaging == 34 35 42 36 43 == Mailing lists == … … 38 45 == SVN == 39 46 47 * MapServer currently uses: 48 {{{ 49 http://svn.osgeo.org/mapserver/trunk/mapserver/ 50 http://svn.osgeo.org/mapserver/trunk/msautotest/ 51 http://svn.osgeo.org/mapserver/trunk/docs/ 52 ... 53 http://svn.osgeo.org/mapserver/branches/branch-6-0/mapserver/ 54 http://svn.osgeo.org/mapserver/branches/branch-6-0/msautotest/ 55 http://svn.osgeo.org/mapserver/branches/branch-6-0/docs/ 56 ... 57 http://svn.osgeo.org/mapserver/tags/rel-6-0-1/mapserver/ 58 http://svn.osgeo.org/mapserver/tags/rel-6-0-1/msautotest/ 59 (no tagging for docs) 60 }}} 61 * RFC 70 suggests, for TinyOWS: 62 {{{ 63 svn.osgeo.org/mapserver/trunk/tinyows 64 svn.osgeo.org/mapserver/branches/tinyows-1.0 65 svn.osgeo.org/mapserver/tags/tinyows-1.0.0 66 }}} 67 * RFC 71 suggests, for mod_geocache: 68 {{{ 69 svn.osgeo.org/trunk/mapserver/mod-geocache 70 }}} 71 which should probably be: 72 {{{ 73 svn.osgeo.org/mapserver/trunk/mod-geocache 74 svn.osgeo.org/mapserver/branches/mod-geocache-0.4 75 svn.osgeo.org/mapserver/tags/mod-geocache-0.4.0 76 }}} 77 * If we adopt the above then how do we deal with branching and tagging for the combined MapServer suite? 78 79 80 == Test suite(s) == 81 * We currently have msautotest 82 * Do we want combined or separate test suites? 83 40 84 == Tickets (Trac) == 41 85