all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Periodical releases
Date: Mon, 2 Jan 2012 11:54:36 -0800	[thread overview]
Message-ID: <E1B686E6-54F1-432D-8484-B21FBA6F42D9@gmail.com> (raw)
In-Reply-To: <71588355363047528F16FE989690A488@us.oracle.com>

As far as I can tell, the primary motivator for more frequent releases of emacs itself is `so emacs doesn't drift so far from its sub-parts', like as Gnus, Org, CEDET, CC-mode (in the past), etc.  This is a laudable goal, but emacs doesn't seem to currently have the developer cycles necessary to handle this - releases are frequently held up by documentation changes and reviews even now, with the infrequent releases we have.

Hopefully, the included package system can cover this gap, once it's fully spread through the userbase; users will be able to easily opt-in to newer Gnus releases (for example) via elpa(s)/packages.  If we get this working reliably, we could even remove some packages from the emacs core, in favor of more frequent package-based releases.  While this model might have once seemed burdensome to users, several years of such systems (for example, in web browser extension updates) will have already trained them to deal with such things before emacs starts doing something similar.

That's my hope, anyway.

*Chad




  reply	other threads:[~2012-01-02 19:54 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 [this message]
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
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=E1B686E6-54F1-432D-8484-B21FBA6F42D9@gmail.com \
    --to=yandros@gmail.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.