[Biopython-dev] Retiring our old RedMine bug tracker
Peter Cock
p.j.a.cock at googlemail.com
Wed Jul 20 18:23:12 UTC 2016
Thanks Travis,
That's the idea, yes. Once you've filed a new GitHub
issue, go back to old issue on RedMine to comment
with the GitHub issue link, and then close the RedMine
issue.
(If you can't close issues ping me, and I should be
able to give you permission to do that).
If there's a particular part of Biopython you're interested
in, or have used yourself, I suggest you focus there.
Otherwise just browse the open issues.
If we get several volunteers working on this at the same
time, we might need a more explicit plan to avoid
duplicating effort.
Peter
On Wed, Jul 20, 2016 at 7:19 PM, Travis Wrightsman <twrig002 at ucr.edu> wrote:
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.open-bio.org/pipermail/biopython-dev/attachments/20160720/59b1368a/attachment.html>
More information about the Biopython-dev
mailing list