[Biopython-dev] Retiring our old RedMine bug tracker

[Peter Cock]

Thanks for volunteering Travis, Markus,

If old issues on RedMine can be closed as already fixed, that's
easy - just close them.

If old issues on RedMine seem relevant, copy as much information
as possible to a new issue on GitHub (because the old RedMine
will be shut down), and then mark the old issue on RedMine as
resolved with a link to the replacement issue on GitHub.

This means the RedMine issue count should reduce to zero,
at which point the old server can be turned off (assuming the
other projects have also finished migrating their old issues).

(email me if you need more permissions on RedMine to do this)

Bonus points: If you can find the original reporter's GitHub account,
then also @mention them on the new issue.

Adding a GitHub issue tag seems sensible, would something like
"From-RedMine" work?

Peter

On Wed, Jul 20, 2016 at 9:34 PM, Travis Wrightsman <twrig002 at ucr.edu> wrote:
> Markus,
>
> I agree we should have a category or tag for issues transferred to GitHub.
> For now, I have closed issues that have been resolved in GitHub and changed
> the Redmine Issue's URL to the relevant GitHub commit/pull request/issue.
> For issues that are still open I plan to just migrate the discussion (if
> any) and open a new issue on GitHub (see this issue I just made).
>
> -Travis
>
> On Wed, Jul 20, 2016 at 12:16 PM, Markus Piotrowski
> <Markus.Piotrowski at ruhr-uni-bochum.de> wrote:
>>
>> I would also volunteer but I'm unsure what exactly is the job?
>> Should there be a special tag to put to the title of a transferred issue?
>> How to delete the issues on RedMine or mark them as transferred?
>> Copy the whole RedMine issue including its discussion into the GitHub
>> issue?
>>
>> -Markus
>>
>> Am 20.07.2016 um 20:19 schrieb Travis Wrightsman:
>>
>> I should be able to donate some time to this. Will the volunteers be
>> reading through each issue to see if it was solved and creating new issues
>> on the GitHub repository if it's still an open issue?
>>
>> -Travis
>>
>> (First one didn't reply to all)
>>
>> On Wed, Jul 20, 2016 at 3:59 AM, Peter Cock <p.j.a.cock at googlemail.com>
>> wrote:
>>>
>>> Hello Biopythoneers,
>>>
>>> After we moved our code repository to GitHub, we started using
>>> their issue track which integrates with pull requests etc:
>>>
>>> https://github.com/biopython/biopython/issues
>>>
>>> Prior to that we were using an OBF hosted RedMine instance
>>> (itself migrated from an even older Bugzilla server):
>>>
>>> https://redmine.open-bio.org/projects/biopython
>>>
>>> Once you click though any annoying certificate warning, you'll
>>> see there are still about 90 open issues and 20 feature requests.
>>>
>>> The OBF would like to shut down the RedMine server since no
>>> one is actively using it any more, and it is costing us money
>>> in AWS fees.
>>>
>>> Several years ago we talked about manually triaging these, i.e.
>>> refiling and cross referencing any relevant issues on GitHub,
>>> and closing irrelevant issues:
>>>
>>> http://lists.open-bio.org/pipermail/biopython-dev/2013-August/019939.html
>>>
>>> Do we have any volunteers to help with this?
>>>
>>> In the absence of any volunteers to review the old RedMine
>>> issues, Plan B is to follow BioPerl's lead and do an automated
>>> migration to a dedicated GitHub repository just for the old
>>> issues:
>>>
>>> https://github.com/bioperl/bioperl-live-redmine
>>>
>>> Who can help out?
>>>
>>> Thank you,
>>>
>>> Peter
>>>
>>> (Speaking here primarily as a Biopython developer, but I am
>>> also secretary for the Open Bioinformatics Foundation board)
>>> _______________________________________________
>>> Biopython-dev mailing list
>>> Biopython-dev at mailman.open-bio.org
>>> http://mailman.open-bio.org/mailman/listinfo/biopython-dev
>>
>>
>>
>>
>> --
>> Travis Wrightsman
>> University of California, Riverside
>>
>>
>> _______________________________________________
>> Biopython-dev mailing list
>> Biopython-dev at mailman.open-bio.org
>> http://mailman.open-bio.org/mailman/listinfo/biopython-dev
>>
>>
>>
>> _______________________________________________
>> Biopython-dev mailing list
>> Biopython-dev at mailman.open-bio.org
>> http://mailman.open-bio.org/mailman/listinfo/biopython-dev
>
>
>
>
> --
> Travis Wrightsman
> University of California, Riverside
>
> _______________________________________________
> Biopython-dev mailing list
> Biopython-dev at mailman.open-bio.org
> http://mailman.open-bio.org/mailman/listinfo/biopython-dev