[GRASS-dev] svn/trac -> git/github migration plan

[Markus Neteler]

On Wed, May 15, 2019 at 10:20 PM Luca Delucchi <lucadeluge at gmail.com> wrote:
> On Wed, 15 May 2019 at 21:40, Veronica Andreo <veroandreo at gmail.com> wrote:
> >> Another thing is the need for new contributing guidelines. Git is not Subversion and committing to master won't work (please, let me know if you want me to show some examples).
> >
> > I am very interested in such examples, esp. how the workflow will be from now on for example when making a small change in manuals.
>
> Yes, it is important to know this. How to use branches and also how to
> update local version from the master one. Should we use a private
> clone and make pull request to the main repository o use the main
> repository directly?

AFAIK it is recommended to open an own "feature branch" in the own
fork and then open a pull request.

Concerning backports we could check the bot magic used by other OSGeo projects.

Markus