Since roadmaps and RFCs seem to be the order of the day...

Those of you involved in the various packaging and detangling efforts may
be interested to know what's happening with my DVS package in the near
future.  OOPSLA got me started on some refactoring and rethinking, and the
results so far are this:

- I've split the PackageInfo class out from the rest of DVS, so that it
can be used on its own by other packages.  There are already tools out
there that depend only on it (like SpaghettiTracer) and others that could
be made to (like Ned's SARBuilder).  That way people can do package
analysis, etc, without having the whole DVS UI/chunk-parser/etc loaded.
I will probably also include a lightweight fileOut tool as an alternative
to the full DVS system.

- Colin Putney and I have started extending PackageInfo with some useful
analysis tools: queries like #externalUsers (outside methods that
reference classes in the package) and #externalCallers (outside methods
that send messages unique to the package).  This could be useful, along
with SpaghettiTracer, for the image carvers - Colin used this to split out
PWS.

- After a discussion with Michael Rueger at OOPSLA, I've made a good start
at a simple declarative source model and versioning system; the idea is to
move to a non-fileout based, pure-Squeak CVS-like tool.  I got the
auto-merging working today, and it's looking pretty good.  The name of the
system is Monticello.

I'll start releasing this stuff in the next couple of weeks as it
stabilizes, and as I update docs.  Those with packages that currently
depend on DVS may want to coordinate with me so we can release a stable
set of tools together.  It would be nice if SM had some dependency support
by then too... ;)

Cheers,
Avi