Avogadro 0.9.5 - tagging on Monday 1 June

Hi,

This is just to announce that I plan to tag the Avogadro 0.9.5 release
on Monday. I would appreciate everyone getting everything pushed this
weekend. I will be working on integrating your changes, testing builds
on our supported platforms and finishing off the features I want to get
in this weekend.

I plan on working on the API/headers, the surfaces/cubes GUI, an update
notification extension (notify users that an updated Avogadro version is
available), POV-Ray clean ups, z-matrix (may be) and ensuring the new
patches all look good. I would also encourage people to go through our
open bugs/feature requests and see what we can close, what needs
attention etc.

The rough time line I have outlined is:

1 June - tag and release Avogadro 0.9.5.
7 June - feature/string freeze - no new strings or string changes. Only
minor UI changes.
9 June - baby arrives - limited availability - hope everyone else takes
care of fixes/docs for a week or two
19 June - rough date - tag 0.9.6 - hopefully last beta - work out
remaining bugs
1 July - tag Avogadro 1.0.0, package it, gain last minute feedback - TEST.
4 July - release Avogadro 1.0.0!

Once features/strings are frozen I would like to push bug fixes,
polishing, testing, unit testing. Along with that we need a big push to
add documentation, screencasts and solicitation of feedback before the
1.0.0 release.

After 9 June I am not certain of my availability for a while, everyone
else should still be around though. Plenty of people can push to my git
repo, if you would like to be added as a collaborator then just ask. I
would encourage you to get friends and colleagues to test Avogadro, blog
about it, tweet etc.

Let me know if you spot any issues with the time line. Otherwise I will
add this to our wiki.

Have a great weekend, add cool things to Avogadro lets get our first
stable release ready!

Best wishes,

Marcus

CMakeFiles/avogadro.dir/molecule.cpp.o:/usr/lib/gcc/i686-pc-linux-
gnu/4.4.0/…/…/…/…/include/c++/4.4.0/ext/atomicity.h:46: more
undefined references to `__sync_fetch_and_add_4’ follow

Considering that we never call anything like this, I’d think this is
an external bug (GCC? Qt? Boost?)

How have you configured Avogadro? What version of Qt are you using?

-Geoff

Moin

Currently I am hitting this:

==================================

CMakeFiles/avogadro.dir/molecule.cpp.o:/usr/lib/gcc/i686-pc-linux-gnu/4.4.0/…/…/…/…/include/c++/4.4.0/ext/atomicity.h:46: more undefined references to `__sync_fetch_and_add_4’ follow

==================================

More complete log attached.

Ziel: i686-pc-linux-gnu
Konfiguriert mit: …/configure --prefix=/usr --enable-shared
–enable-languages=c,c++,fortran,objc,obj-c++ --enable-threads=posix
–mandir=/usr/share/man --infodir=/usr/share/info --enable-__cxa_atexit
–disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib
–enable-clocale=gnu --disable-libstdcxx-pch --with-tune=generic
Thread-Modell: posix
gcc-Version 4.4.0 20090505 (prerelease) (GCC)

Carsten

Carsten Niehaus wrote:

Moin

Currently I am hitting this:

==================================

CMakeFiles/avogadro.dir/molecule.cpp.o:/usr/lib/gcc/i686-pc-linux-gnu/4.4.0/…/…/…/…/include/c++/4.4.0/ext/atomicity.h:46: more undefined references to `__sync_fetch_and_add_4’ follow

==================================

Hi Carsten,

I saw this too, on Arch. It is some kind of issue with Arch/GCC 4.4.
This is a really low level function from Googling and nothing to do with
us as far as I can tell.

Marcus

On Tue, Jun 2, 2009 at 7:36 AM, Marcus D. Hanwell marcus@cryos.org wrote:

Carsten Niehaus wrote:

Moin

Currently I am hitting this:

==================================

CMakeFiles/avogadro.dir/molecule.cpp.o:/usr/lib/gcc/i686-pc-linux-gnu/4.4.0/…/…/…/…/include/c++/4.4.0/ext/atomicity.h:46: more undefined references to `__sync_fetch_and_add_4’ follow

==================================

Hi Carsten,

I saw this too, on Arch. It is some kind of issue with Arch/GCC 4.4.
This is a really low level function from Googling and nothing to do with
us as far as I can tell.

I had this problem the other day too – also on arch. A system update
fixed it. It showed up right in the middle of when I was working on
OpenBabel and made me wonder what the hell I broke :slight_smile:

Dave

1 June - tag and release Avogadro 0.9.5.
7 June - feature/string freeze - no new strings or string changes.
Only
minor UI changes.

I think we should push this back one day until 8 June. I think it will
help to have the freeze on a weekday. I’m slightly concerned by the
number of changes I’m pushing myself – I’d like to make sure we don’t
suddenly need a new error message or something.

19 June - rough date - tag 0.9.6 - hopefully last beta - work out
remaining bugs

I think there will definitely need to be wide-spread testing of this
release (now 0.9.7). We’d like to make sure there aren’t any
"showstopper" or “wear-a-bag-on-your-face” bugs.

-Geoff

On Sat, Jun 06, 2009 at 11:17:24PM -0400, Geoffrey Hutchison wrote:

19 June - rough date - tag 0.9.6 - hopefully last beta - work out
remaining bugs

I think there will definitely need to be wide-spread testing of this
release (now 0.9.7). We’d like to make sure there aren’t any
"showstopper" or “wear-a-bag-on-your-face” bugs.

I’d suggest having another beta/release candidate after the
OpenBabel-2.2.2 release which requires it; this way, it can be made sure
everybody is doing the final testing from the same OB baseline.

Michael

Michael Banck wrote:

On Sat, Jun 06, 2009 at 11:17:24PM -0400, Geoffrey Hutchison wrote:

19 June - rough date - tag 0.9.6 - hopefully last beta - work out
remaining bugs

I think there will definitely need to be wide-spread testing of this
release (now 0.9.7). We’d like to make sure there aren’t any
"showstopper" or “wear-a-bag-on-your-face” bugs.

I’d suggest having another beta/release candidate after the
OpenBabel-2.2.2 release which requires it; this way, it can be made sure
everybody is doing the final testing from the same OB baseline.

I don’t have any objections - I provided dates as a time line to work
to. To be honest if there were any terrible bugs like that I had assumed
we would break string freeze, possibly delaying release until it could
be worked out. I think an updated openbabel release would help. I think
the Windows and Mac binaries are using OpenBabel 2.2.x branch head, and
Linux is currently trailing in this respect.

Thanks,

Marcus