Upcoming 0.6 release

Development
1

Hi,

I haven’t heard strenuous objections to releasing our current efforts
as 0.6 – largely because we’ve made huge advances over the 0.3
release in terms of functionality.

Since it’s Wed, Feb. 27th, I’d like to ask if there are HUGE
SHOWSTOPPER bugs that we absolutely MUST fix before Friday.

I will make sure to make a “March 1” snapshot of Open Babel 2.2.0b4 to
go along with the Avogadro release. It’ll probably be March 1st in
Japan by the time we make 0.6 of Avogadro anyway.

Cheers,
-Geoff

2

On Wed, Feb 27, 2008 at 11:14 PM, Geoffrey Hutchison
geoff.hutchison@gmail.com wrote:

Hi,

I haven’t heard strenuous objections to releasing our current efforts
as 0.6 – largely because we’ve made huge advances over the 0.3
release in terms of functionality.

Since it’s Wed, Feb. 27th, I’d like to ask if there are HUGE
SHOWSTOPPER bugs that we absolutely MUST fix before Friday.

  • The DrawTool adjust hydrogen’s undo/redo still isn’t working
  • I believe Donald pointer out that AutoOpt creates a thread every
    step. The thread should have an event loop which we can
    start()/quit(), I’ll try to look if I can get this working, but can’t
    promise anything.
  • I’ve added most of the engines/tools have
    readSettings/writeSettings. There are still some left to do, testing
    them would also be good. Should I (or we) make a list of settings that
    aren’t working? Although these are small details, It would look very
    sloppy to have some working and some not I think.

That’s all I can remember at the moment but there is probably more :frowning:

Tim

I will make sure to make a “March 1” snapshot of Open Babel 2.2.0b4 to
go along with the Avogadro release. It’ll probably be March 1st in
Japan by the time we make 0.6 of Avogadro anyway.

3

On Feb 27, 2008, at 6:34 PM, Tim Vandermeersch wrote:

Oh, yes. The torsion constraints/restraints haven’t been implemented
yet. This should be done before release or we should remove the option
from avogadro.

Let’s remove them for now. It’s a great feature to have, but I don’t
think anyone will notice and I doubt we’ll have it fixed yet. I’m
happy to temporarily disable incomplete features.

Cheers,
-Geoff