[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: patch vs. overwrite in bzr

From: Thierry Volpiatto
Subject: Re: patch vs. overwrite in bzr
Date: Wed, 04 Apr 2012 10:35:34 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux)

Michael Albinus <address@hidden> writes:

> Bastien <address@hidden> writes:
>>> I may have replied elsewhere.  The way I see it, Org should be taken out
>>> of `trunk' and instead the Emacs release should include a set of ELPA
>>> packages (including Org).
>> IMHO this move would just send a signal to Emacs devs "do not try to 
>> fix this, it's just an ELPA package" -- which does not so good to me.
> I share the same fear that a package residing in the elpa branch could
> be regarded as second class citizen. OTOH, being an elpa package would
> require from us (external) package maintainers shorter freeze windows,
> before a new Emacs release is shipped. New Tramp features are stalled
> from being synced since June. A similar freeze period was before
> releasing Emacs 23.
> And in the Emacs 22 case, the freeze was for about 3 years, if I'm not
> totally wrong. But maybe I'm just a too pedantic German, following every
> freeze policy ...
I never understood why Emacs have not a developing branch to continue
developing new features during the feature freeze.
I think Emacs lost a lot a new features during this process, especially
from contributors that send patches; most patches are lost or
are unusable after several months of modifications in trunk.

Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]