From mboxrd@z Thu Jan 1 00:00:00 1970 From: aq Subject: Re: July 1 (no bk day) almost here Date: Thu, 30 Jun 2005 09:41:59 +0900 Message-ID: <9cde8bff050629174113aed440@mail.gmail.com> References: Reply-To: aq Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: "Magenheimer, Dan (HP Labs Fort Collins)" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 6/30/05, Ian Pratt wrote: >=20 > > Did I miss a posting on the plans for what the Xen team will > > be doing starting Friday as far as source code management? > > Does the Xen team have licenses for bk? >=20 > Until the middle of last week, we were planning on running mirrored > bitkeeper and mercurial trees. However, our current understanding is > that we'd need a BK licence for all the mercurial users who's changesets > we were automatically importing into BK. This clearly isn't going to > scale, so we've had to abandon it. >=20 > So, the new plan is a big-bang switch over to mercurial. There's been a > lot of effort invested in this by Michael and James, and it looks like > we'll be good for a public go-live Thursday morning -- I'll send out an > email detailing where the repositories are, and a 'getting started > guide' prepared by Andrew that describes the mercurial equivalents of > simple bk commands. We have a mercurial patchbot that will start sending > out messages to the changelog mailing list as soon as we make the > switchover. >=20 > Pretty much all the revision history information in the BK repository > has successfully been imported into mercurial. Various of us have been > playing around with mercurial for a while now, and although it's a step > backwards from bitkeeper, its currently quite usable, and improving > fast. The mercurial developers have been very responsive in fixing minor > bugs and adding features we've requested, so we think this is the best > way forward. Rest assured we've spent a great deal of time investigating > the alternatives... what a great news. i cannot wait. isnt Thursday today ? ;-) regards, aq