unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Stable releases
Date: Thu, 23 Nov 2006 10:05:52 -0800	[thread overview]
Message-ID: <87wt5mrqbj.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: 87y7q3zjpe.fsf@laas.fr

ludovic.courtes@laas.fr (Ludovic Courtès) writes:

> Adding new C code (as is the case with the text collation bug) might
> indeed break builds on some platforms.

Yes.

Also, for anyone who might not be thinking about it, it's probably
worth keeping in mind that Guile builds on quite a few architectures,
and our current release policy attempts to account for that by calling
for the heaviest testing during the unstable to stable transitions (to
hopefully catch any bugs related to endianness, pointer size,
etc. that haven't been caught during the unstable development
process).

The assumption has been that any changes during a stable series will
be be well enough controlled that they won't be nearly as likely to
need that broader testing.

> If this is the case, then it may be the case that the series can
> hardly be regarded as "stable".  Adding new Scheme modules, however,
> is unlikely to break builds.

I agree that it's certainly less likely, but here are some things we
might want to consider:

  - This policy would raise a somewhat arbitrary
    implementation-related criteria for the addition of new features,
    i.e. "If you can write it in Scheme only, then it can go in,
    otherwise it has to wait."

  - Any added modules probably won't have been nearly as broadly
    tested as the rest of the modules in the tree.

  - A given stable release series would no longer map to a known and
    consistent set of features.  i.e. One wouldn't be able to say with
    certainty that 1.8 doesn't have SRFI-N.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-11-23 18:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 21:38 Stable releases Neil Jerram
2006-11-20  1:46 ` Rob Browning
2006-11-21 21:39   ` Neil Jerram
2006-11-22  6:47     ` Rob Browning
2006-11-27 22:44       ` Neil Jerram
2006-11-30  5:57     ` Rob Browning
2006-12-02 14:06       ` Neil Jerram
2006-11-20 13:04 ` Ludovic Courtès
2006-11-20 17:39   ` Rob Browning
2006-11-21 21:54     ` Neil Jerram
2006-11-22  7:16       ` Rob Browning
2006-11-22 13:37       ` Ludovic Courtès
2006-11-23 18:05         ` Rob Browning [this message]
2006-11-27 22:40           ` Neil Jerram
2006-11-28  9:01             ` Ludovic Courtès
2006-12-02 14:21               ` Neil Jerram
2006-12-04  8:55                 ` Ludovic Courtès
2006-11-27  8:39         ` Ludovic Courtès
2006-11-21 21:33   ` Neil Jerram
2006-11-21 12:06 ` Greg Troxel
2006-11-21 22:01   ` Neil Jerram

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=87wt5mrqbj.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.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).