[Biopython-dev] Time for Biopython 1.65?

[Travis Wrightsman]

Is the doc formatting critical for the next release? I won't be able to look at them for any extended time for a week more at least.

-Travis

> On Dec 10, 2014, at 8:45 AM, Peter Cock <p.j.a.cock at googlemail.com> wrote:
> 
>> On Mon, Nov 17, 2014 at 4:32 PM, Peter Cock <p.j.a.cock at googlemail.com> wrote:
>> Hi all,
>> 
>> Compared to our typical release cycle, we're a bit overdue
>> for releasing Biopython 1.65.
>> 
>> Thanks to the NBDC/DBCLS BioHackathon 2014, I was
>> able to spend most of last week working on the Biopython
>> pull request and issues backlog - so things are looking much
>> better now.
>> 
>> Things I think we need to fix first:
>> 
>> * PhyloXML output under Python 3
>>    https://github.com/biopython/biopython/issues/368
> 
> Done, thank you Eric.
> 
>> Things I would like to have:
>> 
>> * Evan's lazy loading as an experimental feature
>>   https://github.com/biopython/biopython/pull/356
> 
> No comments?
> 
>> * Proof reading of epydoc's reStructuredText API docs
>>   (which should now be much prettier than our last release)
> 
> Travis W has run epydoc and read some of this (thank you),
> but to make it easier here is the current version to read online:
> 
> http://biopython.org/DIST/docs/api_dev/
> 
> (Consider this a temp URL for now)
> 
>> Things worth wider discussion (and maybe a beta release):
>> 
>> * String-like equality for Seq objects
>>   https://github.com/biopython/biopython/pull/359
> 
> Done.
> 
>> Feedback on these or patches on other issues most
>> welcome. Is there anything else I've overlooked which
>> justifies delaying a release?
>> 
>> Tiago kindly did the last couple of releases, but unless
>> we have another volunteer I am willing to do this one.
> 
> I could do this tomorrow, otherwise early next week?
> 
> Peter
> _______________________________________________
> Biopython-dev mailing list
> Biopython-dev at mailman.open-bio.org
> http://mailman.open-bio.org/mailman/listinfo/biopython-dev