Preparing for a 0.9 release to round out the year

Hi,

I just wanted to give everyone a heads up that I am pushing for a 0.9 beta
release. I have started a wiki page with things that should be done before we
can make the release.

http://avogadro.openmolecules.net/wiki/To_Do_For_0.9

If there is anything you feel should be in before a beta1 release please let
me know. It has been quite some time since our last release, and I would like
more people to be able to get at it. Since I rewrote much of the core there
are still some regressions.

I think a beta with a few regressions is acceptable in order to get feedback
from the wider community. I would like a 0.9 without any loss of features
though. So - let me know what the big things are that we need back. If anyone
has the time help with porting the remaining tool, extensions and engine would
be gratefully received.

I think that this will be a great release, and I feel that we are very close
to 1.0. We can always extend after 1.0 but we will not be able to change API
or ABI. As such I think a final push to release with the new API, seek wider
review and then push forward to 1.0 would be great.

Let me know your thoughts.

Thanks,

Marcus

On Sunday 21 December 2008 23:23:01 Marcus D. Hanwell wrote:

I just wanted to give everyone a heads up that I am pushing for a 0.9 beta
release. I have started a wiki page with things that should be done before
we can make the release.

http://avogadro.openmolecules.net/wiki/To_Do_For_0.9

If you look at this page I think most of the big stuff is now done. I have a
few new features I would love to get in too, if I can finish them in time.

If there is anything you feel should be in before a beta1 release please
let me know. It has been quite some time since our last release, and I
would like more people to be able to get at it. Since I rewrote much of the
core there are still some regressions.

I think a beta with a few regressions is acceptable in order to get
feedback from the wider community. I would like a 0.9 without any loss of
features though. So - let me know what the big things are that we need
back. If anyone has the time help with porting the remaining tool,
extensions and engine would be gratefully received.

As far as I can see there are lots of things that are massively improved.
There are still a couple of regressions, but we need to balance that with
making a release and receiving wider testing. I would like to try and get the
source ready for an avogadro-0.9_beta1 release at the end of the week.

If possible we should aim to make some binaries for Windows and Mac so that
they can get wider testing. I didn’t hear any objections and so I will do what
I can to ensure the code base is in good shape for a beta release. Please let
me know about any bugs or regressions you think we should try to iron out
before a 0.9_beta1 release.

Thanks,

Marcus

Hi,

A 0.9.0 preview windows build can be found here:

http://mail.cryos.net/timvdm/avogadro-win32-0.9.0.exe [18MB]

This is the first windows release to include python support and the
installer includes everything needed to use python from avogadro
(PyQt4, numpy, sip). Shaders should also be working although I can’t
test them here. I also included the translations.

While it is not the final 0.9.0 windows installer, feedback is always
welcome to make sure the installer works on various windows versions
and so on…

Technical notes:

  • The reason why we install all the python stuff to “C:\Program
    Files\Avogadro” (instead of c:\Python-X.Y) is that the Qt dll files
    used for building PyQt4 need to be the same as the dll’s to link
    avogadro.

  • Only the QtCore, QtGui and QtOpenGL dll files (+ python .pyd module)
    are included. Should I add more Qt dll’s to allow users to use the
    full PyQt4 API.

  • Standalone python scripts are not supported out-of-the-box, this
    shouldn’t be to hard if you are familiar with python though…

Cheers,
Tim

On Mon, Jan 5, 2009 at 5:18 PM, Marcus D. Hanwell marcus@cryos.org wrote:

On Sunday 21 December 2008 23:23:01 Marcus D. Hanwell wrote:

I just wanted to give everyone a heads up that I am pushing for a 0.9 beta
release. I have started a wiki page with things that should be done before
we can make the release.

http://avogadro.openmolecules.net/wiki/To_Do_For_0.9

If you look at this page I think most of the big stuff is now done. I have a
few new features I would love to get in too, if I can finish them in time.

If there is anything you feel should be in before a beta1 release please
let me know. It has been quite some time since our last release, and I
would like more people to be able to get at it. Since I rewrote much of the
core there are still some regressions.

I think a beta with a few regressions is acceptable in order to get
feedback from the wider community. I would like a 0.9 without any loss of
features though. So - let me know what the big things are that we need
back. If anyone has the time help with porting the remaining tool,
extensions and engine would be gratefully received.

As far as I can see there are lots of things that are massively improved.
There are still a couple of regressions, but we need to balance that with
making a release and receiving wider testing. I would like to try and get the
source ready for an avogadro-0.9_beta1 release at the end of the week.

If possible we should aim to make some binaries for Windows and Mac so that
they can get wider testing. I didn’t hear any objections and so I will do what
I can to ensure the code base is in good shape for a beta release. Please let
me know about any bugs or regressions you think we should try to iron out
before a 0.9_beta1 release.

Thanks,

Marcus



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

Am Saturday 10 January 2009 04:00:22 schrieb Tim Vandermeersch:

  • The reason why we install all the python stuff to “C:\Program
    Files\Avogadro” (instead of c:\Python-X.Y) is that the Qt dll files
    used for building PyQt4 need to be the same as the dll’s to link
    avogadro.

In other words: If Python and/or PyQt4 is already installed those
installations are not affected at all?

Carsten


Sigh. I like to think it’s just the Linux people who want to be on
the “leading edge” so bad they walk right off the precipice.
(Craig E. Groeschel)