On 12/05/19 18:19, Markus Neteler wrote:
On Fri, May 10, 2019 at 5:06 PM Martin Landa <landa.mar...@gmail.com> wrote:
Hi,
út 7. 5. 2019 v 10:26 odesílatel Martin Landa <landa.mar...@gmail.com> napsal:
commits can be referenced to github issues. Issue migration needs to
be also done on private repository. This would require to set up empty
private repo, migrate tickets and than transfer ticket using GitHub
API to public repo. This complicates procedure a bit. I would still
prefer to do source code and issues migration together even it will
take some time.
back to this topic, I added to trac an alternative scenario based on
two steps (source code and issues migration separated) [1]. Opinions
welcome. We are very close to day D.
Excellent.
IMHO the separate migration of source code and issues is the way to go.
Like that we can already work with the then completed migration next
weekend in Berlin and define workflows.
+1
I think we just need to get the ball rolling. There will certainly be
some transition pain, but if we try to prepare everything to perfection
it will never happen ;-)
Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
