From: Carsten Mattner <carstenmattner@googlemail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Periodical releases
Date: Mon, 2 Jan 2012 23:27:26 +0100 [thread overview]
Message-ID: <CACY+Hvpt+LcrPZLxnjvVMVnkUryt7RTQixzo3f-ws7xWjOM64w@mail.gmail.com> (raw)
In-Reply-To: <E6E4C5AD82114BB7BE99C38C49C4627F@us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2883 bytes --]
On Monday, January 2, 2012, Drew Adams <drew.adams@oracle.com> wrote:
>> > But in no case should that difficulty/nuisance of building
>> > be an excuse for releasing the product before it is fully baked.
>>
>> I don't mind building my emacs.
>
> Great. But you did cite "less of a need to build emacs manually" as an
argument
> why releases should be more frequent.
So that distros don't carry ancient emacs versions.
>> It's a nuisance to have years old Emacs version in distributions.
>
> Why? What's the nuisance? Anyway, you build Emacs yourself from trunk
as often
> as you like, and you don't mind doing so. Where's the beef?
I'd like to use the packaged emacs if it wasn't too old (for me).
>> To get a less buggy Emacs a better approach is releasing it
>> more often so that there are more testers who wouldn't even consider
>> building manually or install a prebuilt snapshot from trunk.
>
> Bon sang mais c'est bien sur! Ye olde cathedrale vs bazaar song...
>
> There are already plenty of pre-release bugs reported, needing to be
fixed.
> Maybe when they are fixed you can argue that Emacs should be released to
get
> more testers. For now, there seem to be enough people using pre-release
builds
> that give rise to bug reports. More input is always welcome of course,
but
> Emacs users are not _only_ testers and fixers.
Not much to argue here.
> FWIW, where I work the default, prebuilt Emacs for developers on
GNU/Linux is
> Emacs 21.3.1! And my impression is that few of them bother to build a
more
> recent version. They are seemingly not clamouring for a new version,
especially
> since there are already 6 (!) releases available more recent than the one
they
> use. (Some of them still use XEmacs, and apparently happily so.)
>
> It's sometimes good to step back a bit and imagine that not all, or even
most,
> Emacs users are involved in, or even interested in, Emacs development.
> Ponder... Hard to fathom, I know.
>
> Many, probably most, users use Emacs the way I use my car: just to get
around
> and do the things I need to do. I don't work on the engine; I don't want
to
> understand the electrical system; and I upgrade only when the old horse
just
> can't make it around the block anymore even with a little coaxing.
>
> Now I'm sure carmakers do not consider me their prime marketing target,
and I'm
> perhaps not a typical car owner. But they really do need to sell new
cars, to
> stay in business. They need new models each year - periodic releases.
>
> We're not selling cars, and we're not even in business. We're not in a
race or
> a competition for market share. We cannot go out of business. We
improve Emacs
> only because we want it to be better or we enjoy improving it or both -
> intrinsic reward. And there's no hurry in that.
If we sold cars, looks would b more important than function. It's good this
ain't a car.
[-- Attachment #2: Type: text/html, Size: 3388 bytes --]
next prev parent reply other threads:[~2012-01-02 22:27 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 [this message]
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
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+Hvpt+LcrPZLxnjvVMVnkUryt7RTQixzo3f-ws7xWjOM64w@mail.gmail.com \
--to=carstenmattner@googlemail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).