[Biopython] Volunteers for making Biopython release 1.77

[Peter Cock]

Just an FYI, the docstring automatic update worked perfectly,

https://biopython.org/docs/1.77/api/index.html

Look for the "Deploying application" expandable entry at the end of the
TravisCI API job:

https://travis-ci.org/github/biopython/biopython/jobs/690561073

(Travis will update either dev or the current version automatically, the
script here deliberately does not care about git tags to allow tweaks to be
made if there are any last minute fixes needed in the docstrings).

This has drawn my attention to the API links in the Tutorial - the
reference in Doc/Tutorial/chapter_quick_start.tex is just to
http://biopython.org/DIST/docs/api/ which is the old epydoc pages, and we
could add an FAQ entry too?

Chris - If you have already started building the Tutorial, don't worry - we
can fix that for the next release, and separately if it might be time to
start replacing the epydoc pages with redirects.

Peter

On Sat, May 23, 2020 at 6:31 PM Peter Cock <p.j.a.cock at googlemail.com>
wrote:

> Excellent - let's hope there are no surprises,
>
> Peter
>
> On Sat, May 23, 2020 at 6:28 PM Daley, Christopher <dalchr28 at evergreen.edu>
> wrote:
>
>> I've got time this weekend and already have a branch with most of (A)
>> ready to go.  I'll work through the rest of the steps today with a Monday
>> release date in mind.
>>
>> I've got an i386 container building at the moment to see if there's an
>> obvious cause/fix for https://github.com/biopython/biopython/issues/2863
>>
>> My github username is as good as any I figure.
>>
>> Chris
>> ------------------------------
>> *From:* Peter Cock <p.j.a.cock at googlemail.com>
>> *Sent:* Saturday, May 23, 2020 8:19 AM
>> *To:* Daley, Christopher <dalchr28 at evergreen.edu>
>> *Cc:* Michiel de Hoon <mjldehoon at yahoo.com>; biopython at biopython.org <
>> biopython at biopython.org>
>> *Subject:* Re: [Biopython] Volunteers for making Biopython release 1.77
>>
>> Looks ready to go - no other last minute issues have been raised, have
>> they?
>>
>> I'd like to include this, but won't hold it up to wait:
>>
>> https://github.com/biopython/biopython/pull/2334
>> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbiopython%2Fbiopython%2Fpull%2F2334&data=02%7C01%7Cdalchr28%40evergreen.edu%7Cca77afc11f1a49cbcff008d7ff2cb16d%7C22adcff7c06f49a68f2050711c40ddaa%7C0%7C0%7C637258439728005204&sdata=RpTbMIX%2BijIdCkvblgFDD1J0Vxg89nf2rsKdrNGOR8g%3D&reserved=0>
>>
>> Also any ideas on the remaining Debian / BLAST+ issue welcome:
>>
>> https://github.com/biopython/biopython/issues/2863
>> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbiopython%2Fbiopython%2Fissues%2F2863&data=02%7C01%7Cdalchr28%40evergreen.edu%7Cca77afc11f1a49cbcff008d7ff2cb16d%7C22adcff7c06f49a68f2050711c40ddaa%7C0%7C0%7C637258439728015199&sdata=T7vNcs%2FaGvfEyT7NecUvXgEkW3vbcoHI6OucILGnPFk%3D&reserved=0>
>>
>> Chris - against the background instructions
>> https://biopython.org/wiki/Building_a_release
>> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbiopython.org%2Fwiki%2FBuilding_a_release&data=02%7C01%7Cdalchr28%40evergreen.edu%7Cca77afc11f1a49cbcff008d7ff2cb16d%7C22adcff7c06f49a68f2050711c40ddaa%7C0%7C0%7C637258439728015199&sdata=%2BDb4SZrqly5IzAt5740Bb2jsvYJplm%2F%2BxiWkGn9IVBI%3D&reserved=0>
>> do you want to start with:
>>
>> (A) pull request to the main repository update the version in __init__.py
>> and the tutorial,
>> and NEWS.rst - perhaps dated Monday if you're going to be able to work on
>> it this weekend?
>> Otherwise give yourself a couple of days leeway as some of these steps
>> will need me
>> or another core developer to merge on your behalf.
>>
>> (B) pull request to the DIST repository with updated Tutorial built with
>> that
>>
>> The next steps must wait on those pull requests being merged. Note once
>> (A) is merged,
>> TravisCI should update the API docs for 1.77 automatically:
>> https://github.com/biopython/docs
>> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbiopython%2Fdocs&data=02%7C01%7Cdalchr28%40evergreen.edu%7Cca77afc11f1a49cbcff008d7ff2cb16d%7C22adcff7c06f49a68f2050711c40ddaa%7C0%7C0%7C637258439728025196&sdata=fnmw3xVbvgIUGFEi5gEvz4P0uozsSsrschVgadqJ9oA%3D&reserved=0>
>>
>> (C) Once (A) is merged, pull request the wheel repository to build the
>> wheels
>>
>> (D) Once (A) is merged, pull request to the website with the new tar-ball
>> and zip
>>
>> (E) Draft a release announcement based on the NEWS.rst file, I can set
>> you up with
>> an account on the open-bio.org
>> <https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fopen-bio.org%2F&data=02%7C01%7Cdalchr28%40evergreen.edu%7Cca77afc11f1a49cbcff008d7ff2cb16d%7C22adcff7c06f49a68f2050711c40ddaa%7C0%7C0%7C637258439728035194&sdata=Wrh5h%2F4KE86jKEWZvjWaL48YS5Wh1Vpgo6nwf7weMQ8%3D&reserved=0>
>> WordPress for that - do you want the same username
>> as your GitHub?
>>
>> Peter
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.open-bio.org/pipermail/biopython/attachments/20200524/d66b1146/attachment-0001.htm>