> > I'd especially like to see you discuss how to set up a project gate, and how
> > to manage all the various hooks and options. With teamware, it was always
> > quite simple to set up a project gate, so it would be nice to have a simple
> > procedure to follow in the new world.
>
> Agree wholeheartedly.
>
> > I'd also like to hear about some of the ways in which mercurial is better
> > than teamware, and how it is worse.
> >
>
> I would go further, and suggest "Why bother?", as well. Though I
> don't have an answer.
Just to pile on: I think it's important to talk about Mercurial's
advantages. Many of us accept that this is a change that had to happen
at some level, and are just looking to hang our hat on something that
is better than its TeamWare equivalent. These things _do_ exist --
the ability to restore a workspace to an arbitrary tag, for example --
but they merit reemphasis. Also, I would like to know the issues that
we think are fixable in Mercurial, versus those things that are so
baked in that they cannot change. (I believe that the issue of a single
comment per changeset is in the latter category -- which is a damned
shame -- but it would be good to get a more official word on that.)
Also, has the adoption of Mercurial achieved its original goal of allowing
more development outside the confines of Sun? If so (and I certainly hope
that it's so, given the cost of the transition), that would be good to
hear about in detail...
- Bryan
--------------------------------------------------------------------------
Bryan Cantrill, Sun Microsystems Fishworks. http://blogs.sun.com/bmc
