From: Carsten Mattner <carstenmattner@googlemail.com>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Periodical releases
Date: Thu, 5 Jan 2012 12:31:43 +0100 [thread overview]
Message-ID: <CACY+Hvr0eKZK-13bpD4wGrTbKNWseCYj5SVQvAFUEeA6yAurWg@mail.gmail.com> (raw)
In-Reply-To: <m1fwfuwjb9.fsf@gmail.com>
On Thu, Jan 5, 2012 at 11:11 AM, Leo <sdl.web@gmail.com> wrote:
> On 2012-01-05 17:31 +0800, Bastien wrote:
>> 2) I will probably release Org 8.0 before the end of the feature freeze
>> (say march or april). Not having it in Emacs 24.1 is not such a big
>> deal, agreed, but it creates a situation where people often install
>> Org on top of the one that comes with Emacs, which doesn't feel
>> optimal and leads to many questions, because of conflicting installs.
>>
>> Both are separate, and I can try to take care of (1) myself.
>
> I think in future it may be desirable to make more use of the packaging
> system now that we have one. It is like many of those GNU/Linux
> distributions. The core developers/maintainers are concerned with the
> core packages/functionality (it is better use of their time since they
> usually have better insight of the project) and the rest can be taken
> care by community members. For example the value of including org-mode
> in the source tree is quite little. If it is distributed with the
> packing system people can receive more timely bug fixes free of any
> constraint of the release cycle.
I second that. Cedet, Gnus, Org, themes (hash verification issues?)...
next prev parent reply other threads:[~2012-01-05 11:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 12:00 Periodical releases Carsten Mattner
2012-01-01 22:41 ` Stefan Monnier
2012-01-02 10:40 ` Carsten Mattner
2012-01-02 11:36 ` Eli Zaretskii
2012-01-02 12:57 ` Carsten Mattner
2012-01-02 17:31 ` Eli Zaretskii
2012-01-02 19:05 ` Drew Adams
2012-01-02 19:54 ` chad
2012-01-02 21:36 ` Carsten Mattner
2012-01-02 20:29 ` Eric Schulte
2012-01-02 21:31 ` Carsten Mattner
2012-01-02 20:41 ` Lluís
2012-01-02 21:23 ` Carsten Mattner
2012-01-02 22:14 ` Drew Adams
2012-01-02 22:27 ` Carsten Mattner
2012-01-05 2:34 ` Dave Abrahams
2012-01-05 2:58 ` Chong Yidong
2012-01-05 3:36 ` Dave Abrahams
2012-01-05 4:23 ` Óscar Fuentes
2012-01-05 13:25 ` Eli Zaretskii
2012-01-05 13:41 ` Dave Abrahams
2012-01-05 9:31 ` Bastien
2012-01-05 10:11 ` Leo
2012-01-05 11:31 ` Carsten Mattner [this message]
2012-01-05 12:56 ` Jambunathan K
2012-01-05 14:00 ` Leo
2012-01-05 14:30 ` Jambunathan K
2012-01-05 11:28 ` Carsten Mattner
2012-01-05 14:18 ` Eric Schulte
2012-01-05 11:33 ` Carsten Mattner
2012-01-05 5:43 ` Eli Zaretskii
2012-01-05 12:20 ` Dave Abrahams
2012-01-05 15:34 ` Drew Adams
2012-01-03 22:23 ` Stefan Monnier
2012-01-03 18:18 ` What's in a feature? (was: Periodical releases) Bastien
2012-01-04 3:24 ` Stephen J. Turnbull
2012-01-04 10:03 ` What's in a feature? Bastien
2012-01-04 12:43 ` Juanma Barranquero
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=CACY+Hvr0eKZK-13bpD4wGrTbKNWseCYj5SVQvAFUEeA6yAurWg@mail.gmail.com \
--to=carstenmattner@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.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.
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).