Re: [Swig-devel] New Bug Reports

[Vadim Z. <vz...@ze...>]

On Sat, 05 Jan 2013 00:45:06 +0000 William S Fulton <ws...@fu...> wrote:

WSF> Okey doke. So moving bugs/patches to Github makes sense if it is better 
WSF> integrated with pull requests/patches and generally better all round. I 
WSF> don't have a problem with existing references on SF being lost - 
WSF> presumably you mean for already solved bugs. Incidentally the SF bug 
WSF> numbers changed going from old SF to Allura SF, so the bugs using hte 
WSF> old SF bug numbers are probably not easily found. I think, I havn't 
WSF> really looked into it, I just noticed the numbers in Allura are quite 
WSF> different.

 This would definitely seal it for me then, if the bug numbers were lost
anyhow I don't see any reason to stick to SF.

WSF> What I really don't want is two bug trackers with the ensuing 
WSF> duplications and confusion. Which means if the Github tracker is the 
WSF> chosen one we need to move the SF bugs on to it. I don't know how/if 
WSF> that is possible, could someone please look into it?

 I think I already posted this link https://github.com/ttencate/sf2github
but let me repost it once again with the same disclaimer as before: I
haven't used it personally so I don't know how well does it work in
practice. OTOH it's clearly non destructive and so there shouldn't be any
problem with at least testing it.

WSF> I don't mind clearing out old/out of date bugs, but there will probably 
WSF> still be a couple of hundred valid bugs which would be a disservice to 
WSF> just throw away... however tempting it is to put one's head in the sand.

 Yes, we have some 9 year old bugs that are still relevant (unfortunately)
in our project. But many of the old bugs are not so it could definitely be
a good idea to do some cleanup on the existing bugs before migrating them.
It's not a very fun work though...

 Best,
VZ