[Biopython] Planning Biopython 1.85

[Peter Cock]

Hi Sean,

One idea would be scanning over the open issues and pull requests - fresh
eyes are always useful, even if you focus on topics you are familiar with.
There are likely issues which have been resolved but never got closed, and
pull requests which stalled with blocking issues never addressed. In some
cases they might be worth reviving, but in others we should probably close
them. And on a more positive note, there may be some forgotten pull
requests which are in fact ready to merge with passing tests, which just
need flagging for a developer to merge (although they may need to update
some style issues as our checks have gotten stricter over the years).

Peter

On Thu, Sep 12, 2024 at 8:37 PM Sean Brimer <skbrimer at gmail.com> wrote:

> Hi Peter,
>
> I have been using Biopython for several years now and I would like to
> contribute to the maintenance of it. I'm not a formally trained programmer
> so I'm not sure if I have the needed skills for everything but I'm very
> happy to try! My background is a wet bench virologist who learned to code
> enough to get his work completed. I'm looking to work on a project that
> would allow me to stay practiced and to improve my overall skills.
>
> If you think there could be a place here for me I would love to help.
>
> Cheers,
> Sean Brimer
>
> On Mon, Sep 9, 2024 at 6:55 AM Peter Cock <p.j.a.cock at googlemail.com>
> wrote:
>
>> Dear Biopythoneers,
>>
>> We released Biopython 1.84 at the end of June, so three months later
>> which was our typical cadence in the past would put us due for another
>> release at the end of this month.
>>
>> There are practical reasons to do this too -
>> https://peps.python.org/pep-0719/ - Python 3.13 is being released at the
>> start of October, and there is a minor compilation problem with some of our
>> legacy C code (since addressed) which complicates releasing a Biopython
>> 1.84 wheel for Python 3.13. We can in principle release a Python 3.13
>> compatible release now (compiled against the release candidates ahead of
>> the formal release at the start of October).
>>
>> However, as unfortunately has become common, we have a backlog of open
>> issues and open pull requests. Please speak up with any key issues or
>> overlooked pull requests you think need to be addressed for Biopython 1.85,
>> and if you can help review or tests them, even better!
>>
>> I'd be happy to help a volunteer do the release itself, although I see
>> now that I didn't finish updating
>> https://biopython.org/wiki/Building_a_release alongside doing Biopython
>> 1.84 which changed the way the documentation is built and published. By
>> default, I'll do the Biopython 1.85 release and get that how-to updated.
>>
>> Thank you all,
>>
>> Peter
>>
>> _______________________________________________
>> Biopython mailing list  -  Biopython at biopython.org
>> https://mailman.open-bio.org/mailman/listinfo/biopython
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.open-bio.org/pipermail/biopython/attachments/20240917/51cf8e92/attachment.htm>