From: Thien-Thi Nguyen <ttn@glug.org>
Subject: Re: The future: accessing vectors, arrays, etc from C
Date: Wed, 05 Jan 2005 06:52:36 -0500 [thread overview]
Message-ID: <E1Cm9iO-0003Uf-8s@mail.agora-net.com> (raw)
In-Reply-To: <41DB2F0C.9050304@ossau.uklinux.net> (message from Neil Jerram on Wed, 05 Jan 2005 00:04:28 +0000)
From: Neil Jerram <neil@ossau.uklinux.net>
Date: Wed, 05 Jan 2005 00:04:28 +0000
However, I wonder if perhaps we should have a more explicit and
public policy on the level of change that is (i) acceptable and (ii)
likely, from one major release to the next, so that developers know
what to expect?
probably it is better to simply accurately label what is released,
than to restrict what is released. if the changes are major, bump
the major version number. otherwise, the discrepency between label
and goods inside the package just introduces confusion and mistrust.
along w/ this approach would have to be an acceptance that not everyone
is interested in following the change in lockstep. historically, that
understanding has not been easy for guile maintainers to muster in word
or deed, however. perhaps you will be able to break new ground here.
basically, it is fine to "wander around the design space", as long as
the activity is not misrepresented (or self-mistaken) as leadership.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-01-05 11:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 14:56 The future: accessing vectors, arrays, etc from C Marius Vollmer
2005-01-04 0:31 ` Kevin Ryde
2005-01-04 1:51 ` Marius Vollmer
2005-01-05 0:04 ` Neil Jerram
2005-01-05 4:12 ` Mike Gran
2005-01-05 18:10 ` Marius Vollmer
2005-01-05 11:52 ` Thien-Thi Nguyen [this message]
2005-01-05 18:01 ` Marius Vollmer
2005-01-06 19:13 ` Marius Vollmer
2005-01-06 23:08 ` Neil Jerram
2005-01-08 23:19 ` Neil Jerram
2005-01-11 18:01 ` Marius Vollmer
2005-01-11 19:53 ` Mikael Djurfeldt
2005-01-15 21:27 ` Neil Jerram
2005-01-16 8:06 ` 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=E1Cm9iO-0003Uf-8s@mail.agora-net.com \
--to=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).