From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.lisp.guile.devel Subject: Stable releases Date: Fri, 17 Nov 2006 21:38:16 +0000 Message-ID: <87bqn5n48n.fsf@ossau.uklinux.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1163799946 18560 80.91.229.2 (17 Nov 2006 21:45:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 17 Nov 2006 21:45:46 +0000 (UTC) Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Fri Nov 17 22:45:41 2006 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GlBWc-00052W-Rd for guile-devel@m.gmane.org; Fri, 17 Nov 2006 22:45:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GlBWc-0006Yk-Cr for guile-devel@m.gmane.org; Fri, 17 Nov 2006 16:45:30 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GlBWZ-0006Vr-N6 for guile-devel@gnu.org; Fri, 17 Nov 2006 16:45:27 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GlBWW-0006Og-Gp for guile-devel@gnu.org; Fri, 17 Nov 2006 16:45:27 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GlBWW-0006OT-Cp for guile-devel@gnu.org; Fri, 17 Nov 2006 16:45:24 -0500 Original-Received: from [80.84.72.33] (helo=mail3.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GlBWW-0007U8-8G for guile-devel@gnu.org; Fri, 17 Nov 2006 16:45:24 -0500 Original-Received: from laruns (host86-145-51-69.range86-145.btcentralplus.com [86.145.51.69]) by mail3.uklinux.net (Postfix) with ESMTP id 303D140AAA7 for ; Fri, 17 Nov 2006 21:38:53 +0000 (UTC) Original-Received: from laruns (laruns [127.0.0.1]) by laruns (Postfix) with ESMTP id 59B766F71F for ; Fri, 17 Nov 2006 21:38:16 +0000 (GMT) Original-To: Guile Development User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:6221 Archived-At: I've been wondering whether we could make stable releases on a more predictable basis than we have done in the past. In principle, it seems to me that we should make a new stable release whenever - and as soon as - we make a fix in one of the stable branches. In practice, we might want to temper that a little, by (a) leaving a short while - say 2-3 days - after committing a fix, just in case of a glaring mistake that would be picked up by another developer building (b) postponing a release following one fix if we know that some other fixes will be available every soon - to avoid stupidly frequent releases. If we followed this, I'm pretty sure the result would be more frequent stable releases than in the past. I don't see any problem with that, in fact I think it would be a good thing... but then I've never prepared a release myself. Is the release process sufficiently easy and automated that it would allow us to do this? And what does everyone else think about whether it's a good idea? Regards, Neil _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel