The overall structure that you suggest makes sense to me.
> Why:
> OpenSolaris, the gate needs to be outside, TeamWare doesn't fit such
> a model. (other benefits from mercurial go here? on another section?)
I would spend as little time as possible on the "why". We went through
the SCM evaluation, the move to Mercurial is essentially a done deal,
let's not waste time rehashing the decision.
> What changes:
> High-level what's new, what's different, what's gone.
> tools, features, internal paths(?)
I would focus on high-level changes in this section, and leave details
to the "what you need to do" section.
> Questions, pointers to tools-discuss, etc.
We should set up one or more external web pages by the KTD (or soon
thereafter) with
- high-level differences between Teamware and Mercurial
- Teamware -> hg cheat sheet (the "how do I do that now?" stuff,
probably in more detail than we have time for in the KTD)
- pointers to detailed documentation (e.g., the Mercurial wiki, Bryan
O'Sullivan's book)
Anything that's generically about Teamware and Mercurial (i.e., not
specific to ON) might be better put in the Mercurial wiki, and then we'd
just link to that. But I do want to have a one-stop-shopping page on
opensolaris.org, rather than expecting people to remember multiple URLs.
Question for Bonnie: did you have any plans for how the slides and web
page(s) will get written? It'd be good to have a draft ready by 6th
August (i.e., a week before the KTD).
mike
