Hi,
Heikki Toivonen wrote:
The branch contains the internal/wx dir as it was yesterday.
The trunk is wx 36 + some of the alpha2 bug fixes from robin, john,
reid, davids (or will have these changes, not all yet checked in) so
that we can get some testing on these changes.
Would it be possible to have a tarball with those changes only? (before
we dive into the incremental commits). I think we need to progress with
caution here so that we can back out to clean points on our way.
What John is doing is effectively pulling revisions starting from wx 36
and testing each one, until he hits a revision that has test failures
(these revisions really are from the trunk, actually, and not from the
branch... not that it matters but just wanted to point that out). Once
we find the broken revisions, we can figure out what the fixes are, and
check the fixes onto the branch. Once all issues on the branch are
resolved, we'll merge it back to trunk.
That's the strategy. It also implies that everyone should avoid posting
wx commits into the trunk while John is doing those merges. I know we
can roll back, etc... but having too many moving parts is what got us
into trouble in the first place so, knowing that we will hit a problem
(we're looking for a commit that creates failures...), I'd like not to
have to second guess who or what broke functional tests for the next few
days.
John, you should let us know on a regular basis where you stand on those
tests (especially, when you start...).
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
