[mapserver-dev] MapServer docs and GitHub Process

[michael.smith.erdc at gmail.com]

Agree, big +1

Mike

> On Sep 19, 2020, at 6:00 PM, Tom Kralidis <tomkralidis at gmail.com> wrote:
> 
> Big +1. 
> 
> ..Tom
> 
>> On Sep 19, 2020, at 17:39, Seth G <sethg at geographika.co.uk> wrote:
>> 
>> Hi all,
>> 
>> At the moment pull requests to https://github.com/mapserver/docs/ should be made to the latest active branch (currently 7.6). Documentation for new features however should be made to master (as they won't apply to new features). 
>> Sometimes it is difficult to know if a code change will be backported or not. 
>> 
>> There are several pull requests that have been added to the 7.6 branch that are not in master, and some in master that are not in 7.6. I'm not sure how these possible conflicts are merged following a release (likely a painstaking manual process by Jeff?). 
>> 
>> Would it make sense to follow the same development process as the MapServer codebase, and set up the GitHub "backport" bot? Then if code is backported the doc pull request can be too, and master will contain all updates. 
>> 
>> Seth
>> 
>> 
>> --
>> web:http://geographika.co.uk
>> twitter: @geographika
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev