Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Gnus branches and sync with Emacs
Date: Mon, 20 Jul 2009 22:42:24 +0200	[thread overview]
Message-ID: <87eisbw0gf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <871vobdxpu.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 20 Jul 2009 14:18:53 -0400")

On Mon, Jul 20 2009, Chong Yidong wrote:

>> RS> If Gnus developers want to start adding new features to Gnus CVS now,
>> RS> we also need to have a bug-fix-only Gnus branch as well, say "v5-12",
>> RS> which is synced with Emacs trunk (to be Emacs 23.2).  v5-12 would also
>> RS> be used for future Gnus 5.12.* releases.
>>
>> RS> As there's no Emacs branch (or trunk) for new features, this would
>> RS> imply that we cannot sync Gnus to Emacs for quite some time (dunno how
>> RS> are the plans for the next major version of Emacs).
[...]
> Whether the Gnus trunk should be synched to the Emacs trunk depends on
> how "unstable" the Gnus maintainers intend to get.
>
> My goal---and I think Stefan envisions something similar---is to have a
> relatively short development cycle of a few months, during which we'll
> insert a small number of new features (primarily CEDET) alongside the
> usual bugfixes, followed by a pretest leading to 23.2.  If the Gnus
> maintainers can follow a similar schedule, it might be practical to just
> keep the two trunks in synch.

Personally, I could live with such an arrangement, since i didn't have
much time for Gnus development recently.  But I also don't see much
problem to have two branches (like we did with v5-10 for quite a long
time) if other Gnus developers wish to commit new (potentially
destabilizing) features sooner - I seem to recall that we deferred
some contributions during the last months.  Opinions?

> (The recent change of `mail-user-agent' may or may not be consistent
> with this plan.  What's not clear right now is the amount of changes
> that need to be applied to sort out the incompatibilies between
> mail-mode and message-mode.  If the required changes end up being too
> destabilizing, we should either switch mail-user-agent back, or fall
> back on the alternative plan of using the 23.1 branch for 23.2.)

I don't think the change of `mail-user-agent' an Richard's intends WRT
mail-mode/rf2047/mm-* are consistent with this plan, so I'm quite
puzzled about the plans for the Emacs trunk.

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



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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 12:27 Branch for 23.1? David Engster
2009-07-18 20:21 ` Gnus branches and sync with Emacs (was: Branch for 23.1?) Reiner Steib
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 [this message]
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-21 20:43               ` Christoph Conrad
2009-07-22 15:32                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eisbw0gf.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=cyd@stupidchicken.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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).