From: Stefan Monnier <monnier@iro.umontreal.ca>
To: miles@gnu.org, emacs-devel@gnu.org
Subject: New sync'd branch
Date: Sun, 23 Aug 2009 18:21:03 -0400 [thread overview]
Message-ID: <jwvhbvy9odl.fsf-monnier+emacs@gnu.org> (raw)
We'd like to have a new release in the first half of next year with some
new features. Given the short time, the new features need to be
non-intrusive, like new packages.
Until now, we've had 2 active branches: the EMACS_23_1 and the trunk,
where the first is limited to bugfixes (and mostly unused, really), and
the second is aiming to become the next release.
But two things make me think we should change this arrangement:
1- the desire and need to plan for Emacs-24: if we want to keep
releasing regularly, we need to have 2 active branches, one for
short-term localized improvements, and the other for longer
term changes.
2- the fact that Emacs-23.1 seems not to suffer from any serious
problems that would call for a quick new release from the
EMACS_23_1 branch.
So I believe we should create a new branch EMACS_23 which will play the
role currently played by the trunk, so the trunk can now be open to more
experimental development (bidi, cpp->autoconf conversion, lexbind, ...),
targetted for Emacs-24.
There are some problem with this:
- Changes on the 23 branch need to be sync'd to the trunk. As long as
we haven't switched to Bzr, that means we need Miles to do the sync
for us. Miles, could you do that?
- People installing changes need to carefully choose whether to install
it on the 23 branch (from where it will be sync'd to the "24 branch"
aka "trunk"), or on the trunk. Basically, the most important aspect
is that any bugfix which makes sense on the 23 branch need to be
installed on the 23 branch rather than on the trunk.
- The 23 branch will not see as much testing any more. So we need to be
more conservative on what can go there. And we need to make
a conscious effort to try and use the 23 branch on a regular basis.
Maybe if the trunk is sufficiently unstable, this will not be
too problematic.
What do you all think about this?
Stefan
next reply other threads:[~2009-08-23 22:21 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 22:21 Stefan Monnier [this message]
2009-08-23 22:35 ` New sync'd branch joakim
2009-08-24 13:58 ` Leo
2009-08-24 19:24 ` Dmitry Dzhus
2009-08-25 17:44 ` Stefan Monnier
2009-08-26 8:31 ` Miles Bader
2009-08-26 19:04 ` Stefan Monnier
2009-08-27 3:09 ` Eli Zaretskii
2009-08-27 4:47 ` Miles Bader
2009-08-27 5:38 ` Teemu Likonen
2009-08-28 8:34 ` Eli Zaretskii
2009-08-27 6:33 ` Ken Raeburn
2009-08-27 7:08 ` Teemu Likonen
2009-08-27 7:14 ` Christian Faulhammer
2009-08-27 8:55 ` Ken Raeburn
2009-08-27 9:07 ` Miles Bader
2009-08-27 10:11 ` Stephen J. Turnbull
2009-08-28 9:18 ` Eli Zaretskii
2009-08-27 9:47 ` joakim
2009-08-28 9:04 ` Eli Zaretskii
2009-08-28 9:12 ` Miles Bader
2009-08-28 9:19 ` Teemu Likonen
2009-08-28 9:32 ` Eli Zaretskii
2009-08-28 13:03 ` David Kastrup
2009-08-28 13:46 ` Óscar Fuentes
2009-08-28 14:55 ` Juanma Barranquero
2009-08-28 17:11 ` Óscar Fuentes
2009-08-28 17:49 ` Juanma Barranquero
2009-08-28 18:00 ` David Reitter
2009-08-29 3:56 ` Stephen J. Turnbull
2009-08-29 20:20 ` Richard Stallman
2009-08-28 15:08 ` David Kastrup
2009-08-28 17:21 ` Óscar Fuentes
2009-08-28 19:33 ` David Kastrup
2009-08-28 21:41 ` Óscar Fuentes
2009-08-28 22:20 ` Miles Bader
2009-08-28 22:55 ` Óscar Fuentes
2009-08-29 0:17 ` Miles Bader
2009-08-29 9:08 ` David Kastrup
2009-08-29 15:25 ` Stefan Monnier
2009-08-29 0:46 ` Stefan Monnier
2009-08-28 22:00 ` Miles Bader
2009-08-28 14:01 ` Juanma Barranquero
2009-08-28 14:08 ` Eli Zaretskii
2009-08-28 14:13 ` Juanma Barranquero
2009-08-28 14:33 ` Eli Zaretskii
2009-08-28 14:44 ` Juanma Barranquero
2009-08-28 9:38 ` joakim
2009-08-28 9:48 ` Eli Zaretskii
2009-08-28 10:02 ` Eli Zaretskii
2009-08-28 11:18 ` David Kastrup
2009-08-28 15:59 ` David Reitter
2009-08-27 21:27 ` Stefan Monnier
2009-08-28 8:28 ` Eli Zaretskii
2009-08-27 21:52 ` Glenn Morris
2009-08-27 22:17 ` Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 22:25 Nick Roberts
2009-08-25 9:29 ` joakim
2009-08-25 14:06 ` Chong Yidong
2009-08-25 21:02 ` Nick Roberts
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvhbvy9odl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=miles@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.