unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org, emacs-devel@gnu.org
Cc: Miles Bader <miles@gnu.org>
Subject: Gnus branches and sync with Emacs (was: Branch for 23.1?)
Date: Sat, 18 Jul 2009 22:21:23 +0200	[thread overview]
Message-ID: <87eisdn3ng.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2k534bghy.fsf@gwdg-mac-engster.top.gwdg.de> (David Engster's message of "Mon, 22 Jun 2009 14:27:37 +0200")

On Mon, Jun 22 2009, David Engster wrote:

> The Emacs CVS is now branched for the 23.1 release, so the trunk should
> be open again for development soon.

The Emacs trunk is only open for "non-regression bugfixes":

,----[ http://thread.gmane.org/gmane.emacs.devel/111595/focus=111609 ]
| The trunk is now open for all non-regression bugfixes.  New features can
| also be added to the trunk, but please discuss on emacs-devel first.
`----

,----[ http://thread.gmane.org/gmane.emacs.devel/111595 ]
| As currently planned, we'll use the trunk for developing 23.2.
`----

Is this still the policy for Emacs?

> I don't know the usual procedure for Gnus CVS; I guess there should also
> be a branch emacs_23_1, so the trunk can be opened again for new feature
> commits?

If Gnus developers want to start adding new features to Gnus CVS now,
we also need to have a bug-fix-only Gnus branch as well, say "v5-12",
which is synced with Emacs trunk (to be Emacs 23.2).  v5-12 would also
be used for future Gnus 5.12.* releases.

As there's no Emacs branch (or trunk) for new features, this would
imply that we cannot sync Gnus to Emacs for quite some time (dunno how
are the plans for the next major version of Emacs).

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




       reply	other threads:[~2009-07-18 20:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2k534bghy.fsf@gwdg-mac-engster.top.gwdg.de>
2009-07-18 20:21 ` Reiner Steib [this message]
2009-07-20 17:23   ` Gnus branches and sync with Emacs Ted Zlatanov
2009-07-20 18:18     ` Chong Yidong
2009-07-20 20:42       ` Reiner Steib
2009-07-21  1:06         ` Stefan Monnier
2009-07-21 16:09         ` Ted Zlatanov
2009-07-21 17:27           ` Reiner Steib
2009-07-21 20:07             ` Ted Zlatanov
2009-07-22  7:06           ` Stephen J. Turnbull
2009-07-26 17:08             ` Steinar Bang
2009-07-27  1:46               ` Stephen J. Turnbull

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=87eisdn3ng.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --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 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).