Re: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest

[Ted Zlatanov <tzz@lifelogs.com>]

On Fri, 22 Aug 2008 13:49:22 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> ***** Gnus 5.10.* / Emacs 22

RS> Emacs 22.3 is in pretest now and probably will be released soon.
RS> IIUC, there will be no Emacs 22.4 release.  For the Gnus 5.10 series
RS> (= v5-10 branch in Gnus = Gnus 5.11 in Emacs 22.*), I'd suggest to
RS> proceed as follows:

RS> - Continue with v5-10 as before (including sync to/from the Emacs
RS>   22.3 branch) until Emacs 22.3 has been released.

RS> - Thereafter, do a final Gnus 5.10.12 release.

RS> - Retire the v5-10 branch.  (In case an urgent security fix demands for
RS>   a Gnus 5.10.14 release, we could revive it.)

Works for me.

RS> ***** Gnus 5.12.* (No Gnus) / Emacs 23

RS> The Gnus trunk is synched to Emacs trunk (and back).  Since 3 weeks,
RS> Emacs development is in feature freeze for Emacs 23.1 (announcement on
RS> emacs-devel: <http://article.gmane.org/gmane.emacs.devel/101783>)
RS> I.e. we should not sync any non-bugfixes to Emacs trunk anymore (or at
RS> least they must be approved by the Emacs maintainers, Chong Yidong and
RS> Stefan Monnier).

RS> For the Gnus trunk, we have (at least) two options:

RS> (1) Start the feature freeze for No Gnus (to be release as Gnus 5.12)
RS>     now.  Do the bug fixing on the trunk.  Sync the trunk with Emacs
RS>     trunk (as we do now).  

RS>     Release Gnus 5.12.1 at same time as Emacs 23.1.

RS>     New features must be postponed until we start a new development
RS>     cycle.

RS> (2) Create a separate branch for Emacs 23.  Sync this branch with
RS>     Emacs trunk.  Only bug fixes should be committed to this branch.

RS>     Use the trunk for the next version of Gnus.  New features can be
RS>     added on the trunk immediately.

I'm OK with either.  Maybe (2) is a little better in terms of structure.

Ted