From: Romain Francoise <romain@orebokech.com>
To: ding@gnus.org
Subject: Re: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest
Date: Sun, 24 Aug 2008 22:10:44 +0200 [thread overview]
Message-ID: <87tzdaw4vv.fsf@elegiac.orebokech.com> (raw)
In-Reply-To: <87wsi91d8d.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> (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.
If we want to keep our promise that the Gnus version bundled in
Emacs is a (renumbered) stable release, this is the only viable
option. And I don't think we have any major new features waiting to
be installed which would prevent us from implementing this plan.
Also, creating a separate "renumbered Gnus 5.12 but not quite" line
of development for the bundled Gnus doesn't sound very attractive.
Our numbering scheme is complex enough as it is...
next prev parent reply other threads:[~2008-08-24 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 11:49 Reiner Steib
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 [this message]
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=87tzdaw4vv.fsf@elegiac.orebokech.com \
--to=romain@orebokech.com \
--cc=ding@gnus.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).