Tagging a 0.9.8 release/1.0.0 release candidate - 9 September

Hi,

I have been working hard on getting Avogadro into a more stable state,
fixing any crashers and interface issues. I have also been looking at
some optimizations for some of our drawing routines, polishing the API
before it becomes frozen and fixing platform dependent bugs. I think
overall things are in pretty good shape, although we still desperately
need more documentation (I will work on adding more).

I propose tagging 0.9.8 on 9/9/9, as Geoff pointed out it is a fun date.
It also has the serious advantage of giving us a week to get any
remaining bugs fixed. Please let me know if this date poses a particular
problem for anyone. Please concentrate on fixing bugs, polishing the UI
and also on adding documentation.

I would like to branch 1.0 soon, and open trunk back up to feature
development. We need to have 1.0.0 in a release ready state before that.

Thanks,

Marcus

Hi,

On Wed, Sep 2, 2009 at 8:39 PM, Marcus D. Hanwellmarcus@cryos.org wrote:

Hi,

I have been working hard on getting Avogadro into a more stable state,
fixing any crashers and interface issues. I have also been looking at
some optimizations for some of our drawing routines, polishing the API
before it becomes frozen and fixing platform dependent bugs. I think
overall things are in pretty good shape, although we still desperately
need more documentation (I will work on adding more).

I propose tagging 0.9.8 on 9/9/9, as Geoff pointed out it is a fun date.
It also has the serious advantage of giving us a week to get any
remaining bugs fixed. Please let me know if this date poses a particular
problem for anyone. Please concentrate on fixing bugs, polishing the UI
and also on adding documentation.

I would like to branch 1.0 soon, and open trunk back up to feature
development. We need to have 1.0.0 in a release ready state before that.

Sounds good. Is there anything specific I should have a look at?
Otherwise I’ll start with the bug tracker…

Tim

Thanks,

Marcus


Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july


Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

On Wednesday 02 September 2009 16:37:13 Tim Vandermeersch wrote:

Hi,

On Wed, Sep 2, 2009 at 8:39 PM, Marcus D. Hanwellmarcus@cryos.org wrote:

Hi,

I have been working hard on getting Avogadro into a more stable state,
fixing any crashers and interface issues. I have also been looking at
some optimizations for some of our drawing routines, polishing the API
before it becomes frozen and fixing platform dependent bugs. I think
overall things are in pretty good shape, although we still desperately
need more documentation (I will work on adding more).

I propose tagging 0.9.8 on 9/9/9, as Geoff pointed out it is a fun date.
It also has the serious advantage of giving us a week to get any
remaining bugs fixed. Please let me know if this date poses a particular
problem for anyone. Please concentrate on fixing bugs, polishing the UI
and also on adding documentation.

I would like to branch 1.0 soon, and open trunk back up to feature
development. We need to have 1.0.0 in a release ready state before that.

Sounds good. Is there anything specific I should have a look at?
Otherwise I’ll start with the bug tracker…

Focusing on the bug tracker, and adding documentation would be great. I am
working on merging in some code, tomorrow I will be trying to devote to
Windows debugging and testing. May be check out the state of our Python
bindings too,

Thanks,

Marcus