[Scons-dev] Migrating issues from Tigris to GitHub

Bill Deegan bill at baddogconsulting.com
Sun Dec 17 13:58:35 EST 2017


Great work!
I'll try and set aside some time to review it this week.

-Bill

On Sat, Dec 16, 2017 at 6:44 PM, Andrew Featherstone <
andrew.featherstone at cantab.net> wrote:

> Hi All,
>
> I've been working on how we can migrate the Tigris issues to GitHub. You
> can see the output of this at https://github.com/ajf58/
> tigris-sandbox/issues, To ensure that we're not relying on issue
> attachments being hosted at Tigris, which looks to be deserted by its
> owners (no tweets since 2013 https://twitter.com/tigrisdotorg?lang=en,
> for example), the issue attachments are also migrated to GitHub (
> https://github.com/ajf58/tigris-issue-attachments). The source code used
> for doing this can be found at https://github.com/ajf58/tigris-to-github.
>
> I think the next steps are:
>
>    1. Members of this list review the format of the migrated issues and
>    offer feedback.
>    2. Act on feedback.
>    3. Get feedback on the scons-user mailing list.
>    4. Migrate issues to https://github.com/SCons/scons
>
> The migration process takes ~2 hours currently. This is largely due to the
> rate limits GitHub imposees on their REST API. GitHub allows temporary
> restrictions to be imposed on the repo, so we can do that while the
> migration takes place.
>
> Thoughts?
>
> Cheers,
> Andrew
>
>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20171217/544e318d/attachment.html>


More information about the Scons-dev mailing list