all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: Why wasn't the 25.3 release based on the then-head of the emacs-25 branch?
Date: Sun, 17 Sep 2017 15:44:36 -0700	[thread overview]
Message-ID: <e459887e-403d-a5b7-d1ec-b8d2a8b49267@cs.ucla.edu> (raw)
In-Reply-To: <83y3pdi21z.fsf@gnu.org>

Eli Zaretskii wrote:
> That time included the time to make the tarball and test it.

If making the tarball and testing it takes 1.5 days, then that was 20% of the 
overall delay last time, and there is good opportunity for speeding up the 
process. Such a process should take minutes, not hours.

> How can people outside of
> the project be charged with reviewing our bugs and patches?

These are people quite knowledgeable about security and software maintenance. 
They can be a good source for security reviews. It's another set of eyes, with 
an outside perspective, and that is helpful.

> why wouldn't those people speak up here
> and work with us within our procedures?

They're busy. Also, we haven't exactly been soliciting or welcoming their input. 
The most recent emergency release had a bit of an NIH feel about it.

> No one was arguing for additional bureaucracy.  What we need is data
> and procedures

Whatever it's called it's more work, and we lack the resources to do it. Maybe 
we can look at two disparate releases (Debian and Fedora, say). Above that there 
are diminishing returns. Outside reviewers could help here (some are Fedora 
experts).



  reply	other threads:[~2017-09-17 22:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 20:30 Why wasn't the 25.3 release based on the then-head of the emacs-25 branch? Glenn Morris
2017-09-15  3:24 ` Paul Eggert
2017-09-15  6:23 ` Eli Zaretskii
2017-09-15 21:26   ` Tim Cross
2017-09-16  7:10     ` Eli Zaretskii
2017-09-15 23:39   ` Glenn Morris
2017-09-16  7:09     ` Eli Zaretskii
2017-09-16 20:20       ` Paul Eggert
2017-09-17  2:35         ` Eli Zaretskii
2017-09-17  5:14           ` Paul Eggert
2017-09-17 14:21             ` Eli Zaretskii
2017-09-17 17:40               ` Paul Eggert
2017-09-17 18:59                 ` Eli Zaretskii
2017-09-17 22:44                   ` Paul Eggert [this message]
2017-09-18 15:05                     ` Eli Zaretskii
2017-09-18 17:10                       ` Paul Eggert
2017-09-18 17:48                         ` Eli Zaretskii

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=e459887e-403d-a5b7-d1ec-b8d2a8b49267@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.