Mapnik-users, There has been a lot of great progress in trunk [1] and emerging in new branch Artem has been working on [2] (thanks to the funding of several visionary Mapnik supporters).
Mapnik 0.7.0 will be a stability and usability release for the Core library while bringing many enhancements to the datasource plugins and python bindings. Everyone is strongly encouraged to upgrade to Mapnik 0.7.0 as soon as it is released. If you are interested in seeing details on some of the changes track the CHANGELOG as we update it: http://trac.mapnik.org/browser/trunk/CHANGELOG There have been no backwards incompatible changes to general usage and the python API, but changes to the C++ ABI warrant a new minor version. The Dev team is planning to release our current trunk as Mapnik 0.7.0 as soon as next week. During the release process over the next week we will also be merging Artem's 'mapnik2' branch into trunk. If you are running from trunk prepare for instability with backwards incompatible changes. So, for those of you running production systems on trunk you will likely want to begin pulling from the 0.7.0 branch (which will be created tomorrow). However, the new features that will come to trunk are exciting and we encourage you to follow along :). There are still a few open tickets against 0.7.0 if you have the time to help: http://trac.mapnik.org/milestone/0.7.0 If you want to help, but don't see an obvious way how, feel free to contact me off-list. Thanks! Dane http://dbsgeo.com [1] http://bit.ly/closed_mapnik_tickets [2] http://bit.ly/mapnik_of_the_future _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
