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

[Panagiotis Mavrogiorgos]

Dear all,

I would argue that even core developers should not be using the main repo
as their
personal one and that, at least most of the time, they should instead be
using the same
procedure as every other contributor.

Branches in git branches are really "cheap" (especially compared to e.g.
SVN).  They do
make it very easy to experiment and the more proficient you become with git
you do tend
to use them more and more.  If every core dev starts pushing their personal
branches on
the main repo, very soon  there will be noise that can effectively become
too much for
UIs to properly display. For example, please visit
[QGIS](https://github.com/qgis/QGIS) and click on the branch selector.
They only have
release branches (like GRASS) and the UI is already at its limit. Imagine
having e.g.
100+ more branches there...

with kind regards,
Panos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190517/483e77e6/attachment.html>