From: Andy Wingo <wingo@pobox.com>
To: hanwen@xs4all.nl
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Guile release planning
Date: Wed, 12 Nov 2008 20:11:19 +0100 [thread overview]
Message-ID: <m3myg4ahew.fsf@pobox.com> (raw)
In-Reply-To: <491A5E6B.5010208@xs4all.nl> (Han-Wen Nienhuys's message of "Wed, 12 Nov 2008 02:41:15 -0200")
Hi Han-Wen,
On Wed 12 Nov 2008 05:41, Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> One angle that we could take is time based release planning, like GNOME and
> Fedora do: plan to do one or two releases per year on a rigid
> schedule.
With GNOME there is also a difference, as you know: they do not add API
in micro series, only in minor series, and never change the API or ABI
in incompatible ways. While that should be our intent, it's quite a
burden for a language implementation that exposes as much of its guts as
Guile does.
I think we should preserve Guile's ability to change API or ABI
incompatibly (while providing shims: next mail).
Releasing more often would be great, though.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2008-11-12 19:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 1:23 Guile release planning Neil Jerram
2008-11-11 1:59 ` Mike Gran
2008-11-15 23:03 ` Neil Jerram
2008-11-15 23:19 ` Mike Gran
2008-11-11 3:44 ` Linas Vepstas
2008-11-11 17:10 ` Greg Troxel
2008-11-11 20:00 ` Andy Wingo
2008-11-11 21:05 ` Linas Vepstas
2008-11-11 22:06 ` Andy Wingo
2008-11-11 20:18 ` Ludovic Courtès
2008-11-15 23:16 ` Neil Jerram
2008-11-16 23:33 ` Ludovic Courtès
2008-11-17 20:49 ` Andy Wingo
2008-11-18 10:22 ` Ludovic Courtès
2008-12-08 22:05 ` Neil Jerram
2008-12-09 17:01 ` Ludovic Courtès
2008-11-11 15:32 ` Sebastian Tennant
2008-11-11 20:30 ` Ludovic Courtès
2008-11-16 0:03 ` Neil Jerram
2008-11-16 5:11 ` Linas Vepstas
2008-11-16 12:46 ` Greg Troxel
2008-11-16 23:55 ` Ludovic Courtès
2008-11-12 4:41 ` Han-Wen Nienhuys
2008-11-12 19:11 ` Andy Wingo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3myg4ahew.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=hanwen@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).