[Biopython-dev] CVS freeze for Biopython 1.50

Peter biopython at maubp.freeserve.co.uk
Mon Apr 20 16:04:56 UTC 2009


On Mon, Apr 20, 2009 at 4:08 PM, Bartek Wilczynski
<bartek at rezolwenta.eu.org> wrote:
> Hi Peter,
>
> Looks fine to me.

Cool.

> Thanks for your effort put into this release.

Thanks.  I'd forgotten how much work these can be - the Biopython 1.50
beta release seemed to go much more smoothly, but there I wasn't
aiming quite so high (e.g. it didn't have any GenomeDiagram
documentation in it, and I hadn't really looked at Bio.Motif in
detail).  Michiel did offer this time round, but maybe next time it
should be someone else's turn to do the actual release bit?  What I
mean is the project co-ordination is a bit nebulous, but the actual
mechanics of doing a release are fairly simple (assuming you have a
Windows machine already setup to do the installers), pretty well
documented, and that part could be delegated.  See
http://biopython.org/wiki/Building_a_release

i.e. Maybe in a few months time I (or Michiel) can say "Right, CVS
freeze while XXX does the release", where person XXX gets to scan the
documentation, double check the NEWS files, check the unit tests etc,
before putting together the packages and uploading them to the server.
 And maybe then hand over to our "News Coordinator" to do the release
announcement?  Having more people involved will make it take a little
longer, but should mean less minor things get missed (e.g. a typo in
the NEWS file, or a broken unit test specific to a particular OS or
version of python).

> Bio.Motif certainly benefited from refactoring  initiated by your
> comments before the release.

Well, I hope so :)

Peter




More information about the Biopython-dev mailing list