From: Bastien <bzg@altern.org>
To: Chong Yidong <cyd@gnu.org>
Cc: Dave Abrahams <dave@boostpro.com>, emacs-devel@gnu.org
Subject: Re: Periodical releases
Date: Thu, 05 Jan 2012 10:31:41 +0100 [thread overview]
Message-ID: <877h16337m.fsf@gnu.org> (raw)
In-Reply-To: <87r4ze3lf8.fsf@gnu.org> (Chong Yidong's message of "Thu, 05 Jan 2012 10:58:19 +0800")
Chong Yidong <cyd@gnu.org> writes:
> Frankly, I'm not convinced there's any problem.
I can see two problems:
1) merging Org into Emacs trunk is a bit painful. I'm still looking for
a good workflow -- given the fact that Org is using git and Emacs is
using bzr. Any concret suggestion here is welcome. I didn't grok
Stefan's last suggestion.
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.
As for (2), let me refine my suggestion: what about a main feature
freeze for core functionalities and another one for big modules like
Org, Gnus, etc.? The feature freeze for those module could happen for
a *limited* and *known* period of time -- say 2 months before the Emacs
release date.
> Emacs 23.3 was released
> less than one year ago, and we are already well into the pretest for
> 24.1. Doing considerably better would require resources we don't have.
> Note that all those projects that are being held up as models for their
> periodic release systems have people working on them full time!
Yes. It should also be noted that things are getting at a very good
pace since you and Stefan took over maintainership, I guess everyone
acknowledges it.
--
Bastien
next prev parent reply other threads:[~2012-01-05 9: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 [this message]
2012-01-05 10:11 ` Leo
2012-01-05 11:31 ` Carsten Mattner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877h16337m.fsf@gnu.org \
--to=bzg@altern.org \
--cc=cyd@gnu.org \
--cc=dave@boostpro.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.