Difference between revisions of "MapServer Report 2012"

From OSGeo
Jump to navigation Jump to search
Line 10: Line 10:
 
** MapServer 6.2 released on November 14, 2012. See the [http://www.mapserver.org/development/announce/6-2.html Release Announcement] for the list of new features and enhancements in this release
 
** MapServer 6.2 released on November 14, 2012. See the [http://www.mapserver.org/development/announce/6-2.html Release Announcement] for the list of new features and enhancements in this release
 
* Several minor releases tied to bug fixes and security improvements:
 
* Several minor releases tied to bug fixes and security improvements:
** Release of x.y.z on mmm dd, see [http://lists.osgeo.org/pipermail/mapserver-users/2011-January/067705.html announcement]
+
** Release of 6.0.2 and 5.6.8 on February 8, see [http://lists.osgeo.org/pipermail/mapserver-users/2012-February/071476.html announcement]
** Release of x.y.z+1 ...
+
** Release of 6.0.3 on May 18, see [http://lists.osgeo.org/pipermail/mapserver-users/2012-May/072329.html announcement]
 
* Participation in the [[IslandWood_Code_Sprint_2012| Seattle/IslandWood Code Sprint]] in February 2012
 
* Participation in the [[IslandWood_Code_Sprint_2012| Seattle/IslandWood Code Sprint]] in February 2012
* ??Migration from Trac/SVN to GitHub??
+
* Migration of source repository and tickets management from SVN/Trac to GitHub, see [http://www.mapserver.org/development/rfc/ms-rfc-84.html RFC 84]
  
 
=== Areas for Improvement ===
 
=== Areas for Improvement ===

Revision as of 18:26, 13 May 2013

IMPORTANT: This is a work in progress. Needs more editing, not ready for publishing.


MapServer

  • Contact name: Steve Lime, PSC Chair

Key Accomplishments

  • One major release:
    • MapServer 6.2 released on November 14, 2012. See the Release Announcement for the list of new features and enhancements in this release
  • Several minor releases tied to bug fixes and security improvements:
  • Participation in the Seattle/IslandWood Code Sprint in February 2012
  • Migration of source repository and tickets management from SVN/Trac to GitHub, see RFC 84

Areas for Improvement

  • Keeping documentation up-to-date with development remains a challenge
  • Continue work to attract additional developer talent to the project.
  • Cleanup bug backlog (550+ open bugs), and triage new bugs more effectively.
  • Google Summer of Code: continue to try and attract more students

Opportunities to Help

  • General website, documentation and translations maintenance.
  • New coders always welcome, a good way to start is by contributing bug reports and patches.
  • Experienced users can contribute to the release process by testing the betas and release candidates and reporting their results.

Outlook for 2013