From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: merge from 1.8 branch
Date: Wed, 25 Oct 2006 12:22:28 -0700 [thread overview]
Message-ID: <87zmbkkxor.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87bqo0teml.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 25 Oct 2006 19:49:22 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
>> Of course we could also just shift 1.8 into maintenance mode, start
>> focusing on the main branch, and plan to release 1.10 sooner. I'd
>> be open to that as well.
>
> How would that be different from the current situation? (In other
> words, in what sense is 1.8 not already in maintenance mode?)
I was mostly just thinking about the range of options (in general)
between taking the position that 1.8 should only allow bugfixes, and
that any new development should go into 1.10, and taking a more
liberal position as (in part) a way to release new features sooner (at
least those that don't break backward compatibility). Of course in
the former case, there would be more pressure for a earlier 1.10
release.
Of course each approach has its advantages and disadvantages, both
from the developer's perspective, and the user's perspective.
--
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
prev parent reply other threads:[~2006-10-25 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 0:15 merge from 1.8 branch Kevin Ryde
2006-10-10 19:32 ` Neil Jerram
2006-10-11 19:57 ` Kevin Ryde
2006-10-20 20:47 ` Neil Jerram
2006-10-21 13:17 ` Ludovic Courtès
2006-10-22 17:50 ` Rob Browning
2006-10-25 18:49 ` Neil Jerram
2006-10-25 19:22 ` Rob Browning [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=87zmbkkxor.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).