Critical fixes for 1.1.0 before tagging?

Hi,

It would be good to know what critical fixes people want to get in for
1.1.0. This will be the first of our beta series in the 1.1.x series
while we stabilise all of the new features. I have a couple of patches
I would like to merge,

http://review.source.kitware.com/#/t/781/ - it does reduce
functionality, but fixes a critical bug. I think we can add the
functionality back in properly after 1.1.0 (chain perception).

http://review.source.kitware.com/#/t/782/ - we can bring this back,
but this engine has serious issues leaking GL state.

The rest look like feature enhancements that should go into 1.1.1 in
my opinion. I think it would be good to tag tomorrow, and get this out
the door and move on to 1.1.1 where there are already several
significant feature enhancements.

Any critical bugs you feel must be resolved before tagging? It would
be good to get back to more regular releases and so I don’t think we
should rush to merge a load of features fearing it will be another
year before the next release. As this is 1.1 there is no real need to
freeze on features etc at all either.

Marcus

Hi,

It’s great to see all the good work going into the new release.
There’s loads of really valuable new functionality that will be really
appreciated by the community.

There are two bugs I think would be helpful to squash before the new
release is finalised. The first is the problem with creating duplicate
views of (usu. different parts) of the same molecule with different
colours - which is really useful for highlighting interesting
sections of a molecule:

http://sourceforge.net/tracker/index.php?func=detail&aid=3488334&group_id=165310&atid=835077

David fixed the problem with the selection colour overriding the
custom colour selection, but its still not possible to assign
different custom colours to duplicate views of the same molecule.

The other is the seg fault when viewing properties after optimising a structure:

http://sourceforge.net/tracker/?func=detail&aid=3521044&group_id=165310&atid=835077

It’s not critical, but as it’s relatively easy to trigger this, it’s
likely to be encountered by a significant number of users.

Best wishes,

Jens

On 7 June 2012 19:12, Marcus D. Hanwell mhanwell@gmail.com wrote:

Hi,

It would be good to know what critical fixes people want to get in for
1.1.0. This will be the first of our beta series in the 1.1.x series
while we stabilise all of the new features. I have a couple of patches
I would like to merge,

http://review.source.kitware.com/#/t/781/ - it does reduce
functionality, but fixes a critical bug. I think we can add the
functionality back in properly after 1.1.0 (chain perception).

http://review.source.kitware.com/#/t/782/ - we can bring this back,
but this engine has serious issues leaking GL state.

The rest look like feature enhancements that should go into 1.1.1 in
my opinion. I think it would be good to tag tomorrow, and get this out
the door and move on to 1.1.1 where there are already several
significant feature enhancements.

Any critical bugs you feel must be resolved before tagging? It would
be good to get back to more regular releases and so I don’t think we
should rush to merge a load of features fearing it will be another
year before the next release. As this is 1.1 there is no real need to
freeze on features etc at all either.

Marcus


Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


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