python-mapnik icon indicating copy to clipboard operation
python-mapnik copied to clipboard

Releases

Open pnorman opened this issue 9 years ago • 4 comments

CONTRIBUTING.md states to hit up @flippmoke for new releases.

Right now there are no git tags

What blockers are there to having a release?

cc @woodpeck

pnorman avatar May 14 '16 10:05 pnorman

Yes, any known-building tag would be nice. At the moment HEAD is broken, and there is nothing to do but try random changesets until it builds.

aholtzma avatar Jan 09 '17 18:01 aholtzma

I won't lie, I simply do not have anytime at all to manage python-mapnik currently. I hope that others might take up the torch and work more on the release process around python mapnik. Because Mapbox does not have a strategic use for python mapnik currently it is definitely not reviewed or used as much as it should be!

There is a complex process to make a wheel which was only working for python 2 and try to package binaries in a working way. This is something that would require a lot of thought to properly implement for all versions of python.

flippmoke avatar Jan 09 '17 18:01 flippmoke

I think a 5% solution is fine, just document what changeset to use to build against the stable mapnik release. Is there actually a point where this repo built against 3.0.xx? Right now it looks like the HEAD is meant to build against some development branch of mapnik.

aholtzma avatar Jan 09 '17 19:01 aholtzma

I think @artemp would probably be the best to know now.

flippmoke avatar Jan 09 '17 19:01 flippmoke