From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: buildbot setup Date: Thu, 01 Jul 2010 03:43:06 +0200 Message-ID: References: <4BEBC372.5010402@alice.it> <4BEDBF5C.1040306@alice.it> <838w7lfzdo.fsf@gnu.org> <831vddfjp9.fsf@gnu.org> <4BEE984A.4090005@gmx.at> <87eihd143p.fsf@elegiac.orebokech.com> <8739wcjosg.fsf@lifelogs.com> <87eifo9y2j.fsf_-_@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1277949092 8168 80.91.229.12 (1 Jul 2010 01:51:32 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 1 Jul 2010 01:51:32 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 01 03:51:28 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OU8w4-0006Vc-9n for ged-emacs-devel@m.gmane.org; Thu, 01 Jul 2010 03:51:28 +0200 Original-Received: from localhost ([127.0.0.1]:55202 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OU8w3-0003vG-KX for ged-emacs-devel@m.gmane.org; Wed, 30 Jun 2010 21:51:27 -0400 Original-Received: from [140.186.70.92] (port=46306 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OU8vt-0003rz-Cx for emacs-devel@gnu.org; Wed, 30 Jun 2010 21:51:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OU8vr-0006ev-NU for emacs-devel@gnu.org; Wed, 30 Jun 2010 21:51:17 -0400 Original-Received: from smtp-04.vtx.ch ([194.38.175.93]:50205) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OU8vr-0006eh-IF for emacs-devel@gnu.org; Wed, 30 Jun 2010 21:51:15 -0400 Original-Received: from ceviche.home (dyn.144-85-133-055.dsl.vtx.ch [144.85.133.55]) by smtp-04.vtx.ch (VTX Services SA) with ESMTP id C0FD829AD3F; Thu, 1 Jul 2010 03:51:14 +0200 (CEST) Original-Received: by ceviche.home (Postfix, from userid 20848) id A75FF66332; Thu, 1 Jul 2010 03:43:06 +0200 (CEST) In-Reply-To: <87eifo9y2j.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "Wed, 30 Jun 2010 13:26:12 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:126576 Archived-At: > I'm not crazy about using a branch to announce a build success. That's OK. You can also use a tag, of course. > Are developers then supposed to track two branches? The "tested" branch is just an older version of the "trunk", so there really aren't two branches, in terms of development. The "tested" branch is just a read-only mirror that's only updated when some built test succeeded. > Or are users going to track the tested branch but developers the > trunk? That'd be the idea, yes. > What happens if there's a tracking failure, do I need to manually fix > it ASAP? No. > How do we test multiple platforms and coordinate a push when > they are all successful? The "tested" branch should correspond to "no known problem during build&test", so if there's a problem on one platform it should probably be considered as a global failure. But I don't think such problems matter much at this stage. > Or do we keep a separate "tested" branch for each platform and library > combination, Only if you're a masochist. > I think it's better and less confusing to simply announce failures > through another channel, perhaps as bugs. Then silence will be the > default, which is good for everyone, and builds will not have any > effect on the repository. Many people who track Emacs's trunk don't read the mailing-list (or not regularly enough) and they get annoyed when the build fails. Stefan