From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Stable branch will freeze.
Date: Thu, 14 Mar 2002 16:05:46 -0800 [thread overview]
Message-ID: <E16lfEA-0007cY-00@giblet> (raw)
In-Reply-To: <87vgbywwxp.fsf@zagadka.ping.de> (message from Marius Vollmer on 15 Mar 2002 00:29:06 +0100)
From: Marius Vollmer <mvo@zagadka.ping.de>
Date: 15 Mar 2002 00:29:06 +0100
I just made the lonely decision to be more rigorous about the "stable"
branch_release-1-6 branch.
We need to be much more rigorous about really keeping the stable
branch stable. From now on, only release critical, uncontroversial
fixes will be allowed. I intend to be firm on this. We are not
getting anywhere without restraining us from putting new stuff into
the stable branch.
Of course, it is already controversial exactly what is release
critical. I'll just be deciding this. :)
sorry, it sounds like you have some delusions of absolute control here.
please get well soon (or demonstrate your position by removing my write
privs so i can unsubscribe from guile development and use in good
conscience -- TIA).
Consequences: the guile-snarf changes need to be brought back to a
state where guile-snarf is completely compatible with the last
guile-snarf that has been installed. It can add features, but must
not remove any. Also it should define SCM_MAGIC_SNARFER in addition
to SCM_MAGIC_SNARF_INIT when pre-processing the C file. The fact that
SCM_MAGIC_SNARFER is defined should be documented, while
SCM_MAGIC_SNARF_INIT should not be documented. Thien-Thi, I can make
these changes if you want me to. Please feel free to hack on
guile-snarf in the HEAD branch. I really think your work on the
snarfer is important, please don't get me wrong.
i don't want you to make these changes because the changes do not
support encapsulation and robustness, but i suspect you'll make them
anyway. in the future someone will complain and someone will decide
they need to be changed back. will you do those changes then, too?
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-15 0:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 23:29 Stable branch will freeze Marius Vollmer
2002-03-14 23:47 ` Neil Jerram
2002-03-15 0:02 ` Rob Browning
2002-03-15 19:38 ` Marius Vollmer
2002-03-15 0:02 ` Rob Browning
2002-03-15 0:05 ` Thien-Thi Nguyen [this message]
2002-03-15 9:24 ` Neil Jerram
2002-03-15 11:47 ` Thien-Thi Nguyen
2002-03-15 11:59 ` Thien-Thi Nguyen
[not found] ` <87adt9eq8e.fsf@raven.i.defaultvalue.org>
2002-04-03 3:20 ` Thien-Thi Nguyen
2002-04-03 4:22 ` Rob Browning
2002-03-15 19:54 ` Marius Vollmer
2002-03-15 23:19 ` Thien-Thi Nguyen
2002-03-16 0:08 ` Marius Vollmer
2002-03-16 0:39 ` Thien-Thi Nguyen
2002-03-16 18:12 ` Evan Prodromou
2002-03-18 20:19 ` Rob Browning
2002-03-20 21:53 ` Marius Vollmer
2002-04-03 3:33 ` Thien-Thi Nguyen
2002-04-03 4:25 ` Rob Browning
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=E16lfEA-0007cY-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).