[Biopython] Planning Biopython 1.85

--===============8016587086731516861==
Content-Type: multipart/alternative; boundary="00000000000045dcd30621ae6f3a"

--00000000000045dcd30621ae6f3a
Content-Type: text/plain; charset="UTF-8"

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

--00000000000045dcd30621ae6f3a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear Biopythoneers,</div><div><br></div><div>We relea=
sed 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.</div><div><br></div><div>There are practical reasons to do =
this too - <a href=3D"https://peps.python.org/pep-0719/">https://peps.pytho=
n.org/pep-0719/</a> - 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 Pyt=
hon 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).</div><div><br></div><div>However, as unfortunately has =
become common, we have a backlog of open issues and open pull requests. Ple=
ase 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 th=
em, even better!</div><div><br></div><div>I&#39;d be happy to help a volunt=
eer do the release itself, although I see now that I didn&#39;t finish upda=
ting <a href=3D"https://biopython.org/wiki/Building_a_release">https://biop=
ython.org/wiki/Building_a_release</a> alongside doing Biopython 1.84 which =
changed the way the documentation is built and published. By default, I&#39=
;ll do the Biopython 1.85 release and get that how-to updated.<br></div><di=
v><br></div><div>Thank you all,</div><div><br></div><div>Peter</div><div><b=
r></div></div>

--00000000000045dcd30621ae6f3a--

--===============8016587086731516861==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Biopython mailing list  -  [email protected]
https://mailman.open-bio.org/mailman/listinfo/biopython

--===============8016587086731516861==--