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,gmane.lisp.guile.user Subject: Re: Guile release planning Date: Sat, 15 Nov 2008 23:03:53 +0000 Message-ID: <49dd78620811151503v43a809ep2715d98142f8da83@mail.gmail.com> References: <49dd78620811101723m6b014589ua01037d5ea3f17b9@mail.gmail.com> <552701.83918.qm@web37906.mail.mud.yahoo.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1226790294 10030 80.91.229.12 (15 Nov 2008 23:04:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 15 Nov 2008 23:04:54 +0000 (UTC) Cc: guile-user , guile-devel To: "Mike Gran" Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sun Nov 16 00:05:58 2008 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1L1UCm-0005YV-M6 for guile-devel@m.gmane.org; Sun, 16 Nov 2008 00:05:47 +0100 Original-Received: from localhost ([127.0.0.1]:43994 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L1UBd-0005oL-IZ for guile-devel@m.gmane.org; Sat, 15 Nov 2008 18:04:17 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L1UBJ-0005h8-NZ for guile-devel@gnu.org; Sat, 15 Nov 2008 18:03:57 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L1UBI-0005gf-11 for guile-devel@gnu.org; Sat, 15 Nov 2008 18:03:57 -0500 Original-Received: from [199.232.76.173] (port=45166 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L1UBH-0005gW-Tv for guile-devel@gnu.org; Sat, 15 Nov 2008 18:03:55 -0500 Original-Received: from rv-out-0708.google.com ([209.85.198.250]:35858) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L1UBH-0007qO-1q for guile-devel@gnu.org; Sat, 15 Nov 2008 18:03:55 -0500 Original-Received: by rv-out-0708.google.com with SMTP id k29so2200872rvb.6 for ; Sat, 15 Nov 2008 15:03:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8Msx3bE6USXvGKZ9HvlJz95BPnqnuY6qV0s8UxXIjmc=; b=xODO+QjlGiAlnd1gZ0C28+TinxZBVF5PHnIYDt10mVDrF4PA3V+HETyNOMR2bxuy/n qeQiZKWm6maGmX23mUqLCnJcY/x7OzAe+8/x89dObbXQZQKjFfwd4gwMOz9tXYvpeZvZ geH43lpB3iPUBUBJtiIjoHJBcdHFPzoHtCGC8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=oTEhEYu+2pqV+DJ4iOPyPJxea/WF9CK5dR5UYIsPVXc7GhCrN5xTLjhAvnBMyp4im5 sVn9BsyGrX6PYMFJ5+/tFv2x4ypcKIAyD2E0nBFM3qjndQn7uwV9kNXNQnjGckW8HySV iOQ6PNU/JMG3re4vHw0fPKjRUD7wrPNjdAKMQ= Original-Received: by 10.140.144.6 with SMTP id r6mr1369311rvd.185.1226790233140; Sat, 15 Nov 2008 15:03:53 -0800 (PST) Original-Received: by 10.140.142.15 with HTTP; Sat, 15 Nov 2008 15:03:53 -0800 (PST) In-Reply-To: <552701.83918.qm@web37906.mail.mud.yahoo.com> Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:7844 gmane.lisp.guile.user:6916 Archived-At: Hi Mike, thanks for your response. 2008/11/11 Mike Gran : > If the base Guile C API remains stable, it doesn't matter to me how the releases occur, because they won't break my libraries or projects. OK. > If the Guile C API needs to change, some sort of notification and beta pre-release would be preferred, so that I can test my projects before the new Guile gets yum'ed out to my group. How exactly would a "beta pre-release" help? It seems you have in mind people who are building your project from source, using a distro-updated libguile. Even with notification/pre-release, and with you having updated your code accordingly, one of your users might not have downloaded your updated code. I guess I can see, though, that it's nice if you have a bit of notice, and hence time to prepare an update. And then I can also see that to do that you will want real code to work with, not just an English description of the API change. I would propose, then, that we clearly flag (on the mailing list) an API change at the time when the relevant commit is made to the repository, and make sure that some minimum period of time elapses before the subsequent release. I would hope that you could then work on the basis of the commit, without needing a formal pre-release. (Any kind of release takes a bit of time, and pre-releases might confuse the overall release picture.) Would that work? Neil