From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel,gmane.lisp.guile.user Subject: Re: GNU Guile 2.1.7 released (beta) Date: Thu, 23 Feb 2017 19:54:25 +0100 Message-ID: <87tw7kviu6.fsf@pobox.com> References: <87y3x3zt6v.fsf@pobox.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1487877133 12192 195.159.176.226 (23 Feb 2017 19:12:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 23 Feb 2017 19:12:13 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) Cc: guile-devel@gnu.org To: guile-user@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Feb 23 20:12:09 2017 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cgyo9-0002Qr-1b for guile-devel@m.gmane.org; Thu, 23 Feb 2017 20:12:05 +0100 Original-Received: from localhost ([::1]:60446 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cgyoF-0004ZM-0J for guile-devel@m.gmane.org; Thu, 23 Feb 2017 14:12:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50427) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cgyXM-0004zQ-6n for guile-devel@gnu.org; Thu, 23 Feb 2017 13:54:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cgyXH-0006TC-CJ for guile-devel@gnu.org; Thu, 23 Feb 2017 13:54:44 -0500 Original-Received: from pb-sasl1.pobox.com ([64.147.108.66]:60167 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cgyXH-0006RB-6D; Thu, 23 Feb 2017 13:54:39 -0500 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 9F4BF62A32; Thu, 23 Feb 2017 13:54:33 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=6V0NTdmH2Qyh4vKO4CpaU/13tKs=; b=P5SWqC 76kFjtgUR8I70HJXCYeS7uIGV9Jr8us2v+NhPok/+G2QHAcbGiVi0F6IS9TsJZWR TPPT0khiFws+EDJ9O6AmolWPpQsQ+hmih7Xmq5S8OKntCC03VOmWwJhIxy1BCUA1 U4garRud2z9gcinLiWtrI5ihnl94KFthxyUVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=Ejx8nYlrzXPKx0TFbt99kvwAc+Fs0D/O XNvIlvb4YGNoHPeuOpSCelE0DLKHPIDU4BIRwI1OYmmr0+GEnRM9U9WYKmul6mpV dg4zGgXR2sY+TV4LKeb2z2qtCLvjnQJ07sJaT3KnmDD3hCd8c4eovWW+SaspSyuy 2E0XSujty9A= Original-Received: from pb-sasl1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 8917862A31; Thu, 23 Feb 2017 13:54:33 -0500 (EST) Original-Received: from clucks (unknown [88.160.190.192]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl1.pobox.com (Postfix) with ESMTPSA id 7739062A30; Thu, 23 Feb 2017 13:54:32 -0500 (EST) In-Reply-To: <87y3x3zt6v.fsf@pobox.com> (Andy Wingo's message of "Sat, 18 Feb 2017 11:31:20 +0100") X-Pobox-Relay-ID: 835F7440-F9F9-11E6-87DE-CDEC6462E9F6-02397024!pb-sasl1.pobox.com X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 64.147.108.66 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.org gmane.lisp.guile.devel:18941 gmane.lisp.guile.user:13315 Archived-At: On Sat 18 Feb 2017 11:31, Andy Wingo writes: > At this point you might ask yourself when 2.2.0 is coming. The answer > is, very soon! A followup mail will propose a timeline and a list of > blocker bugs. I would like to aim for final prerelease in another 4 > weeks and a final release a week after that. Ahem :) I think that the 2.1.x series is ready to go. There are bugs which we should fix of course. Some of those bugs can be fixed within the stable series; some we can't. Of the bugs that we can't, some we can punt to the next stable series, but some are _release blockers_ -- bugs that we need to fix before 2.2.0. Release blocker bugs principally concern ABI. For example the foreign objects facility which was applied to 2.0 and 2.2 and then rolled out from 2.0 because maybe it's not an interface that we want to support in the future -- well that is still part of 2.2 and if we released today we would indeed have to support it. It's that kind of question. So! Release blockers. * Foreign objects. In or out? Let's start a subthread. * The approach to macro-introduced top-level identifiers: OK or no? Again a subthread would be the thing. * GOOPS: are there incompatible changes that we think are bad? Subthread :) There are a number of other bugs that are also important (reproducibility, broken REPL server) that aren't strictly blockers in the sense that we can release a 2.2.x that fixes them. Those are interesting but unless you want to schedule _your_ work/resources to get them done, they are not blockers, as far as I undersand things. I propose to release a 2.1.8 on 9 March. At that point I would like to have all release blockers resolved one way or the other. Then we can release a 2.2.0 whenever, provided that 2.1.8 release actually compiles :) Thoughts? Cheers, Andy