To Do for 1.0

Development
#1

Just a reminder…

http://avogadro.openmolecules.net/wiki/To_Do_For_1.0

If you look at this list (i.e., what we said we wanted to finish for
1.0), we’re almost there! Well, the big exception is Cryos, who hasn’t
posted his To Do list yet. (I took the liberty of adding a few bits
he’s been doing.)

So I don’t think it’s too soon to talk about release scheduling. For a
number of reasons, I’d like to see a release in early July – perhaps
July 4th.

  • June 1st - release 0.9.5 – feature freeze, interface freeze, and
    "string" freeze (for translators)
    (This has the advantage that Cryos will likely be busy most of June
    with a new baby)

During the month of June, we concentrate on bug fixes, documentation,
and tutorials.

  • July 1st - release 0.9.6 – release candidate for 1.0.

This gives us ~ 2 weeks to finish remaining projects for the 1.0
release. I think after that, we really have to draw a line and save
things for the next big release.

Thoughts? Complaints?
-Geoff

“Real Artists Ship.” - Steve Jobs (on the release of the original Mac)
http://www.folklore.org/StoryView.py?story=Real_Artists_Ship.txt

#2

Hi all.

Probably out of subject, but …

The new interface is great and in my opinion much more
intuitive.

I have one complaint : Benoît is not appearing in the French
translators list. No contribution to Launchpad, but he did most
of the pioneering work. This should be acknowledged somewhere.

The new integrated Mac package will certainly draw new users,
but there is a problem with at least the orbital extension: crash
when requesting “Calculate MO”. Report attached.

Looking forward to 1.0 release,
Cheers,

Louis

#3

Geoffrey Hutchison wrote:

Just a reminder…

http://avogadro.openmolecules.net/wiki/To_Do_For_1.0

If you look at this list (i.e., what we said we wanted to finish for
1.0), we’re almost there! Well, the big exception is Cryos, who hasn’t
posted his To Do list yet. (I took the liberty of adding a few bits
he’s been doing.)

I updated my list with a few things I hope to get in there. I will
prioritize API/ABI breaking events.

So I don’t think it’s too soon to talk about release scheduling. For a
number of reasons, I’d like to see a release in early July – perhaps
July 4th.

  • June 1st - release 0.9.5 – feature freeze, interface freeze, and
    "string" freeze (for translators)
    (This has the advantage that Cryos will likely be busy most of June
    with a new baby)

July 4th could be a good date for release. May be we can make the string
freeze 4 June, so that we can have a few days of feedback on the release
before freezing all strings. This would still give translators a good
month. Also the 1.0 branch would then be in string freeze and 1.0.1 etc
would get improved translations as they are completed.

During the month of June, we concentrate on bug fixes, documentation,
and tutorials.

  • July 1st - release 0.9.6 – release candidate for 1.0.

This gives us ~ 2 weeks to finish remaining projects for the 1.0
release. I think after that, we really have to draw a line and save
things for the next big release.

I agree, and am mostly happy with the state of Avogadro as a library. I
have been concentrating on the library recently, and still worry about
scaling but this work could be saved for another release. With the
recent build system improvements I think we are in much better shape as
a library for other applications. I have also been merging bug fixes
from KDE (new snapshot for KDE 4.3).

It is tough to tell when I will disappear, although to be honest I
suspect I will still find time to work on some Avogadro stuff :wink: I have
updated my list, I would welcome any thoughts/fears about our API. There
are a couple of issues I am aware of that will be fixed soon (in bug
reports). There is certainly quite a bit of interface polish that would
be great too.

Thanks,

Marcus

#4

I updated my list with a few things I hope to get in there. I will
prioritize API/ABI breaking events.

Yes, I’d probably push the GLSL engine to the bottom of the list. It
might be fun, and I’m sure the rendering would be cool. But I’d make
sure that the API/ABI can handle the work – and then I’d work on it
for Avogadro 1.2. (To me, changing the entire rendering approach
sounds like it might take time to debug.)

May be we can make the string freeze 4 June, so that we can have a
few days of feedback on the release
before freezing all strings.

Yes, I think that’s a good idea. Maybe we should give ourselves a full
week for a string/interface freeze. Otherwise, we might be upset if
there’s a bad bug that requires some significant changes.

Also the 1.0 branch would then be in string freeze and 1.0.1 etc
would get improved translations as they are completed.

Exactly. I suspect we’ll still have very complete translations – most
of our strings have remained constant over many releases.

Thanks for updating your To Do items, it’s very helpful.

Cheers,
-Geoff