From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: Miles Bader <miles@gnu.org>, ding@gnus.org
Subject: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest
Date: Fri, 22 Aug 2008 13:49:22 +0200 [thread overview]
Message-ID: <87wsi91d8d.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
we need to decide how to continue Gnus development because of the
Emacs 23 feature freeze.
[I'll be on vacations during September, so it would be good if we
could come to a conclusion during the next few days.]
***** Gnus 5.10.* / Emacs 22
Emacs 22.3 is in pretest now and probably will be released soon.
IIUC, there will be no Emacs 22.4 release. For the Gnus 5.10 series
(= v5-10 branch in Gnus = Gnus 5.11 in Emacs 22.*), I'd suggest to
proceed as follows:
- Continue with v5-10 as before (including sync to/from the Emacs
22.3 branch) until Emacs 22.3 has been released.
- Thereafter, do a final Gnus 5.10.12 release.
- Retire the v5-10 branch. (In case an urgent security fix demands for
a Gnus 5.10.14 release, we could revive it.)
***** Gnus 5.12.* (No Gnus) / Emacs 23
The Gnus trunk is synched to Emacs trunk (and back). Since 3 weeks,
Emacs development is in feature freeze for Emacs 23.1 (announcement on
emacs-devel: <http://article.gmane.org/gmane.emacs.devel/101783>)
I.e. we should not sync any non-bugfixes to Emacs trunk anymore (or at
least they must be approved by the Emacs maintainers, Chong Yidong and
Stefan Monnier).
For the Gnus trunk, we have (at least) two options:
(1) Start the feature freeze for No Gnus (to be release as Gnus 5.12)
now. Do the bug fixing on the trunk. Sync the trunk with Emacs
trunk (as we do now).
Release Gnus 5.12.1 at same time as Emacs 23.1.
New features must be postponed until we start a new development
cycle.
(2) Create a separate branch for Emacs 23. Sync this branch with
Emacs trunk. Only bug fixes should be committed to this branch.
Use the trunk for the next version of Gnus. New features can be
added on the trunk immediately.
Other options?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next reply other threads:[~2008-08-22 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 11:49 Reiner Steib [this message]
2008-08-22 12:20 ` Paul R
2008-08-22 12:56 ` ChangeLog (was: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest) Reiner Steib
2008-08-22 15:32 ` Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest Ted Zlatanov
2008-10-02 10:11 ` Simon Josefsson
2008-10-02 14:38 ` Jason L Tibbitts III
2008-08-22 15:38 ` Ted Zlatanov
2008-08-22 15:49 ` David Engster
2008-08-27 23:00 ` Miles Bader
2008-11-03 20:10 ` Reiner Steib
2008-08-22 16:12 ` Sven Joachim
2008-11-03 20:28 ` Reiner Steib
2008-08-24 20:10 ` Romain Francoise
2008-11-03 20:34 ` Reiner Steib
2008-10-10 18:21 ` Gnus 5.10.12 release plan (was: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest) Reiner Steib
2008-11-03 20:14 ` Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest Reiner Steib
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=87wsi91d8d.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=larsi@gnus.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.
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 NNTP newsgroup(s).