A bit longer than planned, the block on check-ins to the ‘enthought’
repository is now lifted. Everyone who had check-in privileges prior to
the block being set on Monday should again be able to check-in.
The new project structure is in place and the PackageTools project can
succesfully check-out full sets of ETS projects as follows:
* ‘etsco trunk’ — gets the project versions defined as dependencies in
the latest version of ETS (currently 3.0.0b1) Most, but not quite all,
of these were previously under /trunk in the old structure.
* ‘etsco “ets==2.6.1b1″‘ — gets the project versions that correspond to
the in-progress updates to the ETS 2.x series. All of the updated
projects were previously under /branches in the old structure.
* ‘etsco “ets==2.6.0b1″‘ — gets the most recent full release of ETS,
corresponding to the eggs currently available in Enthought’s egg repo.
These were all tags previously, and they still are. 🙂
Some issues that still need to be addressed:
* Cross-project dependencies are not as minimal as we would like. Some
additional refactoring, as customer project schedules permit, will
happen over time to minimize these.
* There are a number of “extras” (in the setuptools sense of the word)
setup for the new projects. Unfortunately, the etsco command doesn’t
handle extras well at this time. I will spend time working to fix this
ASAP. In the meantime, things like ‘etsco Mayavi’ and ‘etsco
Traits[ui,wx]’ don’t do what we would hope.
* Running etsco re-crawls the whole svn repository each time you run it,
which means it can take awhile to run. We’ll work to providing a
pre-computed cache as soon as customer project schedules permit.
* The copy of the old trunk in /sandbox/trunk will disappear shortly,
and without any external notice outside of Enthought. Please do not
rely on this any longer.
Some notes or FYI’s:
* ETS 3.0.0b1, or the current trunk of each project, is not yet released
and has a bit of updating necessary to make all the parts mesh
together. This is pretty much unchanged from the old /trunk. I believe
we’re looking at more than a month, perhaps significantly more depending
on Enthought prioritization and community involvement, before this can
be released and we get the maximum benefit of the new repository structure.
* Based on earlier feedback on this mailing list, ETS 2.6.1b1 probably
gets dumped in favor of a new version number (2.7.0) as a result of
additional features added in enthought.tvtk and enthought.mayavi.
Prabhu and Gael indicated they’d be ready to release in about a month.
* The svn interaction scripts in PackageTools are, in theory, usable for
other repositories besides the ‘enthought’ repo. I’d be interested in
hearing about anyone’s experiences in that regard.
Please feel free to help improve things by submitting patches or