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.user,gmane.lisp.guile.devel Subject: 2.2 git users should switch to stable-2.2 branch Date: Wed, 10 May 2017 21:12:13 +0200 Message-ID: <87vap8plv6.fsf@pobox.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1494443602 13951 195.159.176.226 (10 May 2017 19:13:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 10 May 2017 19:13:22 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) To: guile-devel@gnu.org, guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Wed May 10 21:13:16 2017 Return-path: Envelope-to: guile-user@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 1d8X2y-0003Sc-1t for guile-user@m.gmane.org; Wed, 10 May 2017 21:13:16 +0200 Original-Received: from localhost ([::1]:44333 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d8X33-0000oE-94 for guile-user@m.gmane.org; Wed, 10 May 2017 15:13:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46124) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d8X2G-0000lg-ON for guile-user@gnu.org; Wed, 10 May 2017 15:12:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d8X2F-0005u3-Kx for guile-user@gnu.org; Wed, 10 May 2017 15:12:32 -0400 Original-Received: from pb-sasl2.pobox.com ([64.147.108.67]:58727 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 1d8X2A-0005rp-0C; Wed, 10 May 2017 15:12:26 -0400 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl2.pobox.com (Postfix) with ESMTP id 7DC1468B01; Wed, 10 May 2017 15:12:23 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to :subject:date:message-id:mime-version:content-type; s=sasl; bh=A 5ZYZBvGv5lRv2mEM0HoKCKEbYY=; b=fiYy1jEi2HpheZOBJ5mWp0SRecNvmelZs SqxNQSVksEwTCY4plzWBjm5dr0xf21EbO2eh2vYNgw8uvjByJNXDdVI9+pGq8u46 BoaqZHVKJNsp2ca+nurW3P0rXoh8axKS3nkQ4czCke0RvO6z+AEArINeGyVeur9g a8xyO7vqjg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:subject :date:message-id:mime-version:content-type; q=dns; s=sasl; b=jD/ BXtUuAEUFVRHRFqXAMMUhQJOvAjMq+IjIAHir2um3WddPTASTicuPXRYGY66KA23 E9cNR7cIIPg3ce0I6d3LM4jgRo/c4c+BEWbpoyfBusuRIi1QnZtrH2WcACdWAqCf KLxDu4OhU1xUMTGBwf6Xkmn2G4EuTddpA9DuE/+0= Original-Received: from pb-sasl2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-sasl2.pobox.com (Postfix) with ESMTP id 7779C68B00; Wed, 10 May 2017 15:12:23 -0400 (EDT) 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-sasl2.pobox.com (Postfix) with ESMTPSA id 6F6BA68AFF; Wed, 10 May 2017 15:12:22 -0400 (EDT) X-Pobox-Relay-ID: 987613CE-35B4-11E7-855D-384B894C8D7C-02397024!pb-sasl2.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.67 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:13705 gmane.lisp.guile.devel:19135 Archived-At: Hello Guilefolk, As we did with Guile 1.8 and 2.0, I just pushed a stable-2.2 branch. This is the branch for Guile 2.2 development -- the branch that keeps a stable API and ABI during the 2.2.x series. It's the one you want to be using unless you are doing development of Guile itself. If you have a checkout of Guile master, probably right now you want to do this: git fetch git checkout stable-2.2 Assuming your default remote is the Guile repo, that will fetch the new stable-2.2 branch from git.sv.gnu.org, and then the "checkout" command will check out a new branch locally to track upstream stable-2.2. As far as a roadmap goes... I suspect the next Guile stable series will be 3.0 and I suspect it will feature ahead-of-time compilation to machine code instead of bytecode. I think there will still be a bytecode backend as well for targets that are missing the machine code backend. Here are some thoughts: https://wingolog.org/archives/2016/02/04/guile-compiler-tasks I will probably start within the next month or three on "instruction explosion"; see that blog post for details. It's like Abdulaziz Ghoulum's "incremental approach to compiler development", except completely in reverse :P Farther on I would expect a 3.0 after about 2 years or so. There are many things to do. If someone is interested in taking a task, that blog post has many ideas that are still valid. Incidentally if you use Guile commercially and would like to support my work on it, let me know. My employer Igalia continues to be happy with me working on it a day or two a week, and I work on it as a hobby additionally, but it would be nice to be able to devote all of my attention on Guile, at least for consecutive periods of a month or two so I can work on whole features. I expect a general perf improvement for Guile 3.0 of about 4x relative to Guile 2.2, and with support, this can become reality sooner. There are lots of details of course but if this is something that interests you, let's talk. Happy hacking, and don't forget to switch your Guile git branches! Andy