Bug migration to GitHub.

Done.. (Moved to dev)

Yes. Help is most welcome.
Requirements for successful migration:
1) (if at all possible) keep the same issue numbers and migrate all bugs
(even closed)
2) migrate attachments.

Nice to haves:
1) associate bugs with their github users (This might not be worth the
effort, but if the usernames match maybe?)

Thoughts?

-Bill


On Mon, Dec 4, 2017 at 5:42 AM, Andrew Featherstone <
[email protected]> wrote:

> Hi Bill,
>
> I hadn't realised this was looking for help. I'm happy to take ownership
> of this exercise, and try and import the issues into my fork on GitHub.
> Perhaps I should move this separate topic onto the scons-dev mailing list?
>
> Andrew
>
> On Mon, 04 Dec 2017 05:06:54 -0000, Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
> wrote:
>
> Yes. that's the plan.
> Just no one working on it at the moment.
>
> Dirk has a repo with code for extracting with any eye on migrating to
> roundup (I think), but I'd rather spend less effort supporting
> infrastructure (and patches and security issues with same).
> (It should be in the email archives..
>
> -Bill
>
> On Sun, Dec 3, 2017 at 3:53 PM, Mats Wichmann <[email protected]> wrote:
>
>> On 12/03/2017 10:25 AM, Bill Deegan wrote:
>> > Andrew,
>> >
>> > There's no active work at this time on moving the bug tracker.
>> > There's some work in progress code for extracting from tigris.
>> > Any help is most welcome.
>> >
>> > -Bill
>>
>> If scons is committed to going this way, I might be willing to poke at
>> the other end of the migration - trying to push into github.
>>
>> I say *if* since bug tracking is usually a topic people tend to be
>> pretty passionate about... there are surely some advantages to having an
>> issue tracker more tightly bound to code commits, but in the world of
>> issue trackers, github is not even close to being in the top tier.  Not
>> arguing one way or the other, just want to make sure the project is sure
>> about the direction it wants before spending time on it :)
>>
>>
>> _______________________________________________
>> Scons-users mailing list
>> [email protected]
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>
>
>
>
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev