From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Release-critical bugs
Date: Fri, 19 Sep 2014 12:49:13 -0400 [thread overview]
Message-ID: <k0ha03pncm.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83mw9w25ei.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Sep 2014 20:40:53 +0300")
Eli Zaretskii wrote:
> Suggestions for how to make it faster will be welcome, I'm sure.
A test-suite for absolutely everything, so we can just type `make check'
and be done. ;)
Less flippantly, more concentrated focus on the release, less "a handful
of people try to get the release in shape while the majority play with
the trunk (and argue about VCS)". (But this might just be my biased
impression.) Also a defined release manager position, with the authority
to set deadlines and decide what needs to be done, which I think was
lacking this time. (I don't want the job; it needs to be someone
motivated and with Emacs experience.)
And more documenting of changes closer to the time they happen, by the
person who makes the change, rather than leaving it to the end.
Some way to get more people using the release branch rather than the
trunk. (Maybe the trunk should be the release branch, and the
development should happen elsewhere; but I think this was rejected
before for various reasons?).
We have ~ 200 developers, in theory. I think say 6 months from feature
freeze to release ought to be doable, though I would not want to be
dogmatic about it; it should take as long as it takes.
When it takes too long, people get disheartened and lose focus.
next prev parent reply other threads:[~2014-09-19 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 17:08 Release-critical bugs David Engster
2014-09-17 19:40 ` Glenn Morris
2014-09-18 2:16 ` Ivan Andrus
2014-09-18 17:28 ` Glenn Morris
2014-09-18 2:39 ` Eli Zaretskii
2014-09-18 12:57 ` Rasmus
2014-09-18 14:51 ` Eli Zaretskii
2014-09-18 17:28 ` Glenn Morris
2014-09-18 17:40 ` Eli Zaretskii
2014-09-19 16:49 ` Glenn Morris [this message]
2014-09-19 17:34 ` Eli Zaretskii
2014-09-24 13:48 ` Ted Zlatanov
2014-09-24 15:04 ` Stefan Monnier
2014-09-27 15:10 ` Jens Lechtenboerger
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=k0ha03pncm.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--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.