Return-Path: Delivered-To: apmail-xml-xmlbeans-dev-archive@www.apache.org Received: (qmail 34034 invoked from network); 26 Sep 2003 19:59:56 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 26 Sep 2003 19:59:56 -0000 Received: (qmail 57710 invoked by uid 500); 26 Sep 2003 19:59:45 -0000 Delivered-To: apmail-xml-xmlbeans-dev-archive@xml.apache.org Received: (qmail 57643 invoked by uid 500); 26 Sep 2003 19:59:45 -0000 Mailing-List: contact xmlbeans-dev-help@xml.apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: xmlbeans-dev@xml.apache.org Delivered-To: mailing list xmlbeans-dev@xml.apache.org Received: (qmail 57630 invoked from network); 26 Sep 2003 19:59:45 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Beginning V2 .... Date: Fri, 26 Sep 2003 12:59:49 -0700 Message-ID: <4B2B4C417991364996F035E1EE39E2E11F33BF@uskiex01.amer.bea.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Beginning V2 .... Thread-Index: AcOEZrXkt2dl94+WT+uLDGpRV8SNxQAAI4sw From: "Cezar Andrei" To: X-OriginalArrivalTime: 26 Sep 2003 19:59:50.0642 (UTC) FILETIME=[BEA47520:01C38468] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N David Bau wrote: > Eric wrote: > > I'm planning on getting the V2 code base started by making=20 > a copy of V1 > and checking it in to V2. +1 > Here's what I think we're going to need to do overall while=20 > we ramp up v2: >=20 > (1) Get the old code (copy of v1) checked into v2 and building >=20 > (2) Keep the XMLBeans functionality running while we build "new" stuff > either into it or on the side of it, e.g., in new directories=20 > where new > stuff isn't just minor mods. While doing this, nobody gets=20 > to break DRTs > (i.e., "ant drt") - unless there's a really good reason, in=20 > which case the > DRTs get modified. For example, when you're working on the=20 > new store, you > don't get to break the old store, because other folks will be=20 > depending on > having _some_ store that works. When I (and others) start=20 > reworking binding > to generalize it, we don't get to take away the old binding=20 > code until we > have new code that works better. >=20 > (3) When the new store is ready for prime-time (or any other=20 > big component), > we can plug it in and remove old code either (a) atomically=20 > in a single > commit, not breaking DRTs, or (b) over a transition period where it's > possible to run either the old or new code, and there is a=20 > path that passes > DRTs. The switchover is either atomic or overlapping, but=20 > there should be > no switchover with a gap, so that other developers that are=20 > depending on > basic stuff running can continue to work in parallel. >=20 > In other words, let's make sure any new work is side-by-side with old > working code until it's good enough so that old code can be=20 > deleted. I think > it's what we need to do to be able to make parallel forward=20 > progress on v2. > Sensible? >=20 +1 Is there a way to run the drt automatically after a checkin, something = similar to what they have for Mozilla? ( = http://tinderbox.mozilla.org/showbuilds.cgi?tree=3DSeaMonkey ) Do other Apache projects have something similar?=20 Cezar - --------------------------------------------------------------------- To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/