From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Experimental features
Date: Fri, 22 Jun 2007 17:05:24 -0400 [thread overview]
Message-ID: <jwvaburu2os.fsf-monnier+emacs@gnu.org> (raw)
Release practice during Emacs-21 at least is that new features could only
appear in new major releases, except for a few small exceptions.
I'd like to change that to make released Emacsen evolve faster.
One way to do that would be to introduce the idea of "experimental"
features which could be added to any minor release.
An experimental feature would be disabled by default and the code should be
written in such a way that as long as the feature is enabled, it's clearly
obvious that it cannot have any negative effect.
We'd then provide a way for the user to activate some of the experimental
features from her .emacs file. After some time, we would promote the new
feature such that it is not experimental any more.
Stefan
next reply other threads:[~2007-06-22 21:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 21:05 Stefan Monnier [this message]
2007-06-22 21:22 ` Experimental features Lennart Borgman (gmail)
2007-06-23 4:15 ` Stefan Monnier
2007-06-23 12:40 ` Thien-Thi Nguyen
2007-06-23 19:07 ` Stefan Monnier
2007-06-23 2:51 ` dhruva
2007-06-23 6:00 ` Andreas Röhler
2007-06-24 1:43 ` T. V. Raman
2007-06-24 3:02 ` Eli Zaretskii
2007-06-24 3:59 ` T. V. Raman
2007-06-24 18:42 ` Eli Zaretskii
2007-06-23 13:19 ` Richard Stallman
2007-06-23 13:37 ` Juanma Barranquero
2007-06-24 14:40 ` Richard Stallman
2007-06-24 14:53 ` Juanma Barranquero
2007-06-24 19:25 ` Stefan Monnier
2007-06-23 19:16 ` Stefan Monnier
2007-06-24 14:41 ` Richard Stallman
2007-06-24 19:23 ` Stefan Monnier
2007-06-24 23:47 ` Richard Stallman
2007-06-28 18:51 ` Stefan Monnier
2007-06-29 19:33 ` Richard Stallman
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvaburu2os.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).