Comment 9 for bug 207748

On Wed, Apr 02, 2008 at 11:44:03AM -0000, Andrea Colangelo wrote:
> Gael: a sync could be done, but since we are in Feature Freeze, we must
> go through a Feature Freeze Exception:
> https://wiki.ubuntu.com/FreezeExceptionProcess

I am aware of that, and I fully understand the reasons behind it.

> Could you find a changelog from version 2.0.2a1 to 2.1.1? It would be of
> great help to understand which new features have been added.

Our tracking of changes is pretty poor I am afraid. I can't give you a
list of all the small changes done. Changes from 2.1.0 to 2.1.1 where
just a few bugfixes in python-enthought-traits and
python-enthought-traits-ui, but as mayavi2 depends on these, we had to
make a new release.

The changes from mayavi2.0.2a1 to mayavi2.1.0, and those to the two other
packages it is closely tied to (that is changes from ETS release 2.6.0 to
2.7.0), are exposed in
https://mail.enthought.com/pipermail/enthought-dev/2008-February/012908.html

  * [Envisage] Fixed numerous examples so that they run again.
  * [Envisage] Changed icons to better match downstream licensing
  * policies.
  * [ETSConfig] Minor change to allow the Envisage refresh code plugin
to work without raising a traceback.
  * [Kiva] Fixed examples so that they run again.
  * [Mayavi] Significant documentation improvements.
  * [Mayavi] Increased number and reliability of examples.
  * [Mayavi] Enabled Mayavi to run outside of an Envisage app. It can
now display also in a Traits UI.
  * [Mayavi] Moved enthought.mayavi.tools.mlab to enthought.mayavi.mlab.
  * [Mayavi] Exposed modules and filters via mlab.
  * [Mayavi] Added full support for tensor visualization.
  * [Mayavi] First cut for new options framework.
  * [Mayavi] Using new API for adding widgets to a scene.
  * [Mayavi] Add the possibility to specify to which scene a source
should be added.
  * [Mayavi] Remove wxversioncheck that caused problems in too many
  * cases.
  * [Mayavi] Reimplemented VTKFileReader to be a subclass of
VTKXMLFileReader thus making codebase smaller and more consistent but
also allowing reading of OpenFOAM data.
  * [Mayavi] Added option to enable/disable the auto updating of ranges
used in contours.
  * [Mayavi] Numerous bug fixes and other minor enhancements.
  * [PyFace] Fixed full screen TVTK scenes issues. Full screen should
also work with VTK 5.0.3.
  * [PyFace] Added new TVTK SceneModel and SceneEditor classes that let
one embed a scene and manipulate it from within a Traits UI.
  * [PyFace] Added a configure scene button to the TVTK scene widget so
that users can configure the background and foreground colors, etc.
  * [PyFace] Added a new TVTK SceneEditor that supports actors and 3D
widgets.
  * [PyFace] Removed SimpleScene from the standard api.py module since
it is not commonly used and generates unnecessary warnings.
  * [PyFace] Refactored the TVTK actor_editor and actor_model into
separate modules to facilitate easier porting to PyFace 3.
  * [PyFace] Fixed splitwidget to work with wxPython 2.8.
  * [Traits] Added an auto_close_message function and corresponding UI
dialog.
  * [TVTK] Added support for local VTK classes that a user may have
  * built.
  * [TVTK] First cut at a meaningful README.
  * [TVTK] Fixed bug with DataExtent being treated as a state method.
  * [TVTK] Fixed a problem with unnecessary overloading of certain
traits and methods.
  * [TVTK] Updated dependencies so that TVTK works with in-development
versions of Traits 3 and PyFace 3.

You are not interested in kiva-releated changes, as kiva is not part of
these three Debian packages.

These changes are mostly additions and bug fixes. The most important
change is:

  * [Mayavi] Moved enthought.mayavi.tools.mlab to enthought.mayavi.mlab.

    This will become a backward-incompatible change in the feature
release. For now it only raises a deprecation warning.

I suspect this changelog is quite incomprehensible if you don't know the
details of mayavi and traits. It boils down to:

    * A lot of small bugfixes.
    * Huge documentation improvements
    * Significant bux fix for fullscreen (this was causing a segfault
      under Debian)
    * Addition of new APIs that will in the long run deprecate some old
      ones, but know are just exposed to the user to get feedback (the
      mlab.pipeline submodule, the TVTK SceneModel and the
      MlabSceneModel).
    * Removing some code that was causing crashes because it was using
      deprecated code in VTK. This is not a loss to users, because under
      Linux, it was simply not working.

I am having difficulties making this more clear without going into
technical details. If you have questions about a specific item, don't
hesitate to ask.

Cheers,

Gaël