OSGeoLive issue workflow

By changing its documentation producing work-flow, the OSGeoLive team will also change its work-flow.

This is going to be the new way of working:

Issues on github

1. open an issue about the thing that is going to be fixed

2. or the issue already exists

• git checkout upstream/develop
• git checkout -b issue## where ## is the number of the issue

and in the branch issue## is where you fix the issue and after fixing, you push and make a PR

Issues on trac

We can make the same for trac, if its a trac issue then: trac#### where #### is the track number

Please provide in the comments of the PR a link to the trac issue.

This work-flow provides several things:

• a standard naming on branches that are for fixing issues
• some sense of order to the work

Resources:

• http://nvie.com/posts/a-successful-git-branching-model/