From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: development goals
Date: Mon, 08 Sep 2008 12:27:09 +0200 [thread overview]
Message-ID: <87y723q6f6.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620809071303r148f2aedq6f5b9f3cd4bef3d2@mail.gmail.com
Hey!
"Neil Jerram" <neiljerram@googlemail.com> writes:
> For me, almost all of my time since becoming a maintainer has been
> absorbed by working on bug fixes, largely to do with slightly odd
> platforms (e.g. Mac) or architectures (e.g. ia64). IMO it was
> worthwhile to focus on such bug reports soon after they were reported,
> because (i) the reporters are still around and interested enough to be
> able to provide more info and test fixes, (ii) I believe that running
> on more platforms will be good for the Guile community, and for Guile
> applications.
Same here. But everyone is welcome to help fix bugs! :-)
> Basically, my feeling is that Guile users have been badly burned by
> major release incompatibilities in the past, and I really don't want
> that to happen again. Therefore my "straw man" plan is that
>
> - we stay on 1.8.x for a while
Which IMO means fixing portability bugs and the likes.
> - we treat "master" as a pot of goodies, which we aim incrementally to
> merge across and release as part of the 1.8.x series
The problem is that some of them might be subtly incompatible, mostly
because a lot of internals have been exposed and actually used.
I think it's good to have API and possibly ABI-compatibility within a
major release, so that "1.8.x" really means something, for any value of
`x'; requiring "x >= something" is acceptable IMO (we already have this,
e.g., with modules that got added in 1.8), but "a <= x <= b" isn't.
> - we don't do a big jump to 1.10.x, by just deciding to do so at some
> time (+ a bit of pretesting), because I don't feel confident that we
> can properly consider and document all of the 1.8 .. 1.10
> compatibility issues at once.
I agree that we should reduce the gap between any two major releases.
> But #1 : as I said above, I'm pretty sure Ludovic disagrees with this!
It's not all black & white. ;-)
> I believe that programmers' natural tendency is to plan for infinite
> compatibility.
+1.
(That is especially true in Guile land where many projects are small and
developed only on people's spare time, whom you can't expect to dedicate
time switching APIs.)
> There you're right. We can and should rip GH out now. Actually that
> might make an excellent first example for documenting incompatibility.
> (Anyone who really still needs it can take on the burden of
> maintaining the GH layer themselves.)
IMO, if it doesn't cost anything to keep it (beside `.so' size), let's
keep it.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-09-08 10:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 22:02 [PATCH] Avoid `SCM_VALIDATE_LIST ()' Ludovic Courtès
2008-09-01 0:12 ` Han-Wen Nienhuys
2008-09-01 20:19 ` Neil Jerram
2008-09-01 20:30 ` Ludovic Courtès
2008-09-02 2:40 ` Han-Wen Nienhuys
2008-09-06 22:23 ` Neil Jerram
2008-09-06 21:36 ` Neil Jerram
2008-09-07 4:23 ` Ken Raeburn
2008-09-07 15:24 ` Neil Jerram
2008-09-07 17:30 ` Ken Raeburn
2008-09-07 19:21 ` Neil Jerram
2008-09-08 23:11 ` Neil Jerram
2008-09-09 8:28 ` Ludovic Courtès
2008-09-10 20:43 ` Neil Jerram
2008-09-04 18:24 ` Andy Wingo
2008-09-05 0:10 ` Han-Wen Nienhuys
2008-09-05 1:06 ` Andy Wingo
2008-09-06 22:45 ` Neil Jerram
2008-09-07 2:33 ` Han-Wen Nienhuys
2008-09-07 13:38 ` Neil Jerram
2008-09-07 15:00 ` Han-Wen Nienhuys
2008-09-07 16:19 ` Neil Jerram
2008-09-07 19:25 ` Han-Wen Nienhuys
2008-09-07 14:05 ` Andy Wingo
2008-09-07 15:38 ` development goals (was: [PATCH] Avoid `SCM_VALIDATE_LIST ()') Han-Wen Nienhuys
2008-09-07 20:03 ` Neil Jerram
2008-09-08 4:28 ` development goals Han-Wen Nienhuys
2008-09-08 10:16 ` Ludovic Courtès
2008-09-08 13:57 ` Han-Wen Nienhuys
2008-09-09 7:08 ` Andy Wingo
2008-09-08 10:27 ` Ludovic Courtès [this message]
2008-09-06 22:40 ` [PATCH] Avoid `SCM_VALIDATE_LIST ()' Neil Jerram
2008-09-01 21:09 ` Neil Jerram
2008-09-01 21:47 ` Ludovic Courtès
2008-09-06 22:15 ` Neil Jerram
2008-09-08 9:40 ` Ludovic Courtès
2008-09-06 23:11 ` Mikael Djurfeldt
2008-09-07 2:43 ` Han-Wen Nienhuys
2008-09-07 15:04 ` Neil Jerram
2008-09-07 13:32 ` Neil Jerram
2008-09-02 2:44 ` Han-Wen Nienhuys
2008-09-06 22:32 ` Neil Jerram
2008-09-08 3:13 ` Han-Wen Nienhuys
2008-09-08 4:42 ` Clinton Ebadi
2008-09-08 9:47 ` Ludovic Courtès
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=87y723q6f6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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).