Closed dmorissette closed 7 years ago
Okay, I see that there is a branch-6-2 in the basemaps tree so it seems that this issue can be considered fixed.
However I notice that there is no branch-6-0 so users of MapServer 6.0.x releases are still out of luck (and this ticket was created in response to a request from a 6.0 user)
@tbonfort would it be easy/possible to identify the point in time where 6.0.x compatibility was broken and create a branch-6-0 from that point for MapServer 6.0.x users?
I am using Debian Wheezy, which delivers MapServer 6.0.1. Having a branch-6-0 would be great.
I'll create a branch-6-0, however I'd need the commit that I should branch from
So far the only problem I see in branch-6-2 is the Annotation issue https://github.com/mapserver/basemaps/issues/9 Shall I create a fork from branch-6-2 changing the type to ANNOTATION?
I personally won't maintain 6.0, so do as you prefer. Note that doing it this way, your changes applied to 6.0 won't be easily mergeable into 6-2 and master (as merge branch-6-0 would also merge the commit that switches back to annotation layers)
I see. If you do not see an easier option I'll just change it manually. Since I have to do some other changes to Makefile and *.map that would not belong here I am fine with that. Thanks for your fast response!
Can be closed.
At the moment we do not produce formal releases of basemaps, so basemaps is always a moving target and users of stable MapServer releases (e.g. 6.2) end up getting errors when they try to use the master basemaps from github which contains some changes requiring the master dev version of MapServer.
Ideally the basemaps package should be branched in github and released at the same time as the source code, this way users could have basemaps versions corresponding to their mapserver version.
i.e. When we release "MapServer 6.2" we would also release "Basemaps for MapServer 6.2".