Repository changesets

[Mark Reinhold]

> Date: Wed, 11 Feb 2009 09:21:34 -0800
> From: jonathan.gibbons at sun.com

> What are the basic guidelines for pushing jigsaw repository
> changesets? I presume jcheck is not enabled.

Correct.

>                                              Is it enough to check
> whitespace and use a "reasonable" comment in the summary?

Yep.  We can even live without code reviews, for now.

Just so everyone knows: The plan here is to work on the early stages of
Jigsaw in a riskier, more agile style so that we can make rapid progress.
When we're ready to integrate into the mainline code base then we'll do
so via one giant patch which creates just one changeset in each affected
repository.  Long term, our early development history will only exist in
the Jigsaw Project's archives.

> What about sync-ing with the main jdk7 forest?  If so, who and how
> often?

Good question.  I've been hacking on a clone of b46, and I should be
ready to publish that code soon, so let's consider b46 our starting
point.

We should try to stay reasonably up-to-date.  Syncing every other build
is likely good enough for now.

>         Do you want Hudson to build the jigsaw repositories for
> verification?

That'd be good.  Do you have, or know of, a Hudson instance we could use
for this?

- Mark