From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
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: Mon, 18 Sep 2017 20:48:26 +0300 [thread overview]
Message-ID: <83bmm7j3th.fsf@gnu.org> (raw)
In-Reply-To: <2c3dbffa-b56c-ec31-2fa9-0ca6dc757cd2@cs.ucla.edu> (message from Paul Eggert on Mon, 18 Sep 2017 10:10:21 -0700)
> Cc: rgm@gnu.org, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 18 Sep 2017 10:10:21 -0700
>
> Eli Zaretskii wrote:
> > it's naïve to assume
> > time frames of minutes for these activities, unless we want to give up
> > QA.
>
> It's routine to do the kind of QA that you mention in minutes for projects
> Emacs's size. We're not up to that now, but it's reasonable to make it a goal,
> if this sort of thing is important to us.
With the right organization and equipment available at suitable SLA,
sure. But we are very far from that point, IMO.
> At any rate the procedure could be streamlined considerably compared
> to what it was last time.
Indeed, working in that direction would be a good progress. I don't
think we need to get the time down to minutes, though, as that would
probably require measures that are impractical in our conditions.
> We could try having a better relationship with Debian and one or two others, so
> that the patches they consider to be security issues cause us to consider
> issuing new versions quickly. And we could be more proactive in sending our
> potential security patches to them early in our review process.
If someone could take that upon themselves, sure.
> > Are Debian and Fedora indeed enough? What about Red Hat?
>
> Fedora is Red Hat's early version, so we needn't worry about Red Hat separately.
>
> > What about Arch Linux?
>
> They wouldn't make my cut. Others of us might step up to be a liaison. openSUSE
> is also a plausible candidate for that.
What do others think about the set of distros we should use?
> > given the sample of distributions, how does one
> > figure out which ones of them include a given Emacs changeset, in
> > which versions of Emacs, and since what time.
>
> This info is all public now, at least for Debian and Red Hat.
OK, so it would be good to have the pointers in admin/ somewhere.
Thanks.
prev parent reply other threads:[~2017-09-18 17:48 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
2017-09-18 15:05 ` Eli Zaretskii
2017-09-18 17:10 ` Paul Eggert
2017-09-18 17:48 ` Eli Zaretskii [this message]
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=83bmm7j3th.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--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.