What would be the aim of this migration? I don’t expect anybody new to look into the old bugs that have accumulated on savannah for over twenty years.
I believe the second sentence in your reply aptly captures why it might be a good idea to migrate them in the first place. I'll respect your wishes and we can remain with the legacy system no new person will check.
So this move would only make sense if we wanted to give up on savannah, which you write is not your intention. So what benefits would you expect to be the result of this?
It originally was my intent to abandon the bug tracker on savannah. I was made aware, primarily by you, that that is not what was agreed upon so I backed off on that.
I am not strongly opposed to this step, I just have plenty of more worthwhile tasks to work on.
As do I, but I think it's important to have everything in one place. All I am proposing at this point is a test migration for Gorm bugs only.
Fred, just saying
> Am 20.11.2019 um 05:29 schrieb Gregory Casamento <address@hidden>:
> Hey guys,
> I just realixed... there is a way to download the bugs from savannah. Additionally there is an API for interfacing with the bug system on github. The various ids (for groups or subprojects... gui, base, etc) can be discovered easily.
> If this is something we would like to do, then I can write the script to do the transition. I may try an initial run on gorm's repo just to test it out.
> This would not necessarily mean shutting down the bug tracker at savannah... we would just need to keep them in sync.
> Any thoughts?
> Yours, GC
> Gregory Casamento
> GNUstep Lead Developer / OLC, Principal Consultant
> http://www.gnustep.org - http://heronsperch.blogspot.com