Hi,
I have been very slack these last few months. I had hoped to get out a bug fix
release before Christmas… There is at least one crasher bug (network
fetching of files) that I fixed way back last year that didn’t make it into the
release. It didn’t show until Qt bumped their version and changed behavior,
but I just saw a bug report about it.
So, I would like to tag Avogadro 1.0.1 in the next week or two. This will be a
bug fix only release, but I would appreciate you getting any bug fixes in soon.
I want to ensure there is no ABI/API break, so please be cautious about what
you merge in. It would be good to update the 1.0 translations if possible.
Also, I noticed lots of activity in my new father haze of the last few months.
I wonder if it might also be opportune to make an unstable 1.1.0 release in
the next 3-4 week timescale too? This would be more of a snapshot release in
my opinion, but we could make binaries etc.
I will also be doing what I can to improve our dashboards. I have been working
on splitting Avogadro into subprojects, and would like to get Linux, Windows
and Mac builds going. This also requires people to watch the dashboards and
add tests if we want them to be useful.
Thoughts?
Marcus
18.02.10, 16:12, “Marcus D. Hanwell” mhanwell@gmail.com:
Hi,
I have been very slack these last few months. I had hoped to get out a bug fix
release before Christmas… There is at least one crasher bug (network
fetching of files) that I fixed way back last year that didn’t make it into the
release. It didn’t show until Qt bumped their version and changed behavior,
but I just saw a bug report about it.
So, I would like to tag Avogadro 1.0.1 in the next week or two. This will be a
bug fix only release, but I would appreciate you getting any bug fixes in soon.
I want to ensure there is no ABI/API break, so please be cautious about what
you merge in. It would be good to update the 1.0 translations if possible.
Also, I noticed lots of activity in my new father haze of the last few months.
I wonder if it might also be opportune to make an unstable 1.1.0 release in
the next 3-4 week timescale too? This would be more of a snapshot release in
my opinion, but we could make binaries etc.
I will also be doing what I can to improve our dashboards. I have been working
on splitting Avogadro into subprojects, and would like to get Linux, Windows
and Mac builds going. This also requires people to watch the dashboards and
add tests if we want them to be useful.
Thoughts?
Currently Avogadro trunk make use of many fetures from OB trunk (notably, some spectra types, PC GAMESS support). It’ll be less useful if compiled with OB 2.2.3, so I think OB release is also needed (even minor, 2.2.4)
–
Regards,
Konstantin
Здесь спама нет http://mail.yandex.ru/nospam/sign