From: "Linas Vepstas" <linasvepstas@gmail.com>
To: "Neil Jerram" <neiljerram@googlemail.com>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile release planning
Date: Mon, 10 Nov 2008 21:44:42 -0600 [thread overview]
Message-ID: <3ae3aa420811101944m23d7a72ch992c253326f7e236@mail.gmail.com> (raw)
In-Reply-To: <49dd78620811101723m6b014589ua01037d5ea3f17b9@mail.gmail.com>
2008/11/10 Neil Jerram <neiljerram@googlemail.com>:
>
> I also think it will help us manage API incompatibilities better. I
> think our default position from now on should be to maintain
> source-level (API) compatibility, but it is inevitable that there will
> be exceptions to this.
Any ideas for binary compatibility for the "micro" revisions?
I recently discovered that a library compiled against 1.8.3
would core dump when used with an application compiled
against 1.8.5. Operationally, not a big deal, really; I just
recompiled the lib, but emotionally, it did give me that
sinking feeling for a while, of maybe having yet another
hard-to-find bug, or a system I cannot fully trust. :-(
> the steady new feature model is better.
The linux kernel got rid of the stable/unstable branch idea,
and it's worked really really well. (the reasons why are
widely documented) I'm for it.
--linas
next prev parent reply other threads:[~2008-11-11 3:44 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 [this message]
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
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=3ae3aa420811101944m23d7a72ch992c253326f7e236@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=neiljerram@googlemail.com \
/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).