From: Evan Prodromou <evan@prodromou.san-francisco.ca.us>
Subject: Re: branch_release-1-4 brought into 21st century
Date: Tue, 12 Mar 2002 10:51:26 -0600 [thread overview]
Message-ID: <87adtdohkh.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> (raw)
In-Reply-To: <E16kYht-0005PI-00@giblet> (Thien-Thi Nguyen's message of "Mon, 11 Mar 2002 14:55:53 -0800")
>>>>> "TN" == Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
TN> wrt 1.4.1, probably people would adopt it for bug fixes, and
TN> because it requires minimal changes to their programs, so that
TN> they can continue doing fun new stuff instead of the API
TN> retrofit drudgery. they are also probably waiting for tools
TN> to make migration easier.
That said, a release of 1.4.1 immediately before 1.6.0 would be
somewhat confusing for people.
What about a loud release of 1.6.0, followed (discreetly) by a quiet
release of 1.4.1?
~ESP
--
Evan Prodromou
evan@prodromou.san-francisco.ca.us
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
parent reply other threads:[~2002-03-12 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E16kYht-0005PI-00@giblet>]
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=87adtdohkh.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us \
--to=evan@prodromou.san-francisco.ca.us \
/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).