[Biopython-dev] Git master branch freeze for Biopython 1.69 release

[Peter Cock]

OK, what is hopefully going to be the official Biopython 1.69 release
is now uploaded
and tagged on the main repository master branch:

https://github.com/biopython/biopython/commit/536ead7385084d7547af636eddd6f1706ba2717e
https://github.com/biopython/biopython/tree/biopython-169

Likewise I've uploaded the files so far to the official DIST repo for
the website,

https://github.com/biopython/DIST/commit/3e14bab2a9235915dd93b33306196029ac17e574

They are not yet linked to from the website, but you can browse them here:

https://github.com/biopython/DIST

VOLUNTEERS PLEASE: Could we have a couple of people check some of the
Windows installers work for you, and another try the tar-ball or zip
file and building
from source and running the tests?

The new Tutorial is already live:

http://biopython.org/DIST/docs/tutorial/Tutorial.html
http://biopython.org/DIST/docs/tutorial/Tutorial.pdf

And the API documentation from epydoc:

http://biopython.org/DIST/docs/api/

As usual, this flagged some reStructuredText errors as we don't yet lint that
via TravisCI - see https://github.com/twolfson/restructuredtext-lint/issues/34
and https://github.com/PyCQA/pydocstyle/issues/245

If there are no issues I'll update the website, upload to PyPI, and make the
formal announcement (which will be based on the NEWS.rst file).

Peter

On Thu, Apr 6, 2017 at 9:20 PM, Peter Cock <p.j.a.cock at googlemail.com> wrote:
> Also if anyone wants to volunteer to draft the release announcement for
> email and posting on the OBF blog, that'd be great. Just email any suggested
> text in reply.
>
> Separately, I'm thinking of writing a follow up blog about the dual license
> plan too.
>
> Thanks,
>
> Peter
>
> On Thu, 6 Apr 2017 at 18:18, Peter Cock <p.j.a.cock at googlemail.com> wrote:
>>
>> Please don't commit anything to the master branch for the
>> next 24 hours or so - I've started the Biopython 1.69 release
>> process, but didn't get to finish it today.
>>
>> (Changes committed locally but not yet on GitHub itself.)
>>
>> Thanks,
>>
>> Peter