unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 27264@debbugs.gnu.org
Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Date: Sun, 11 Jun 2017 15:16:00 +0200	[thread overview]
Message-ID: <87zidevf5b.fsf@gnu.org> (raw)
In-Reply-To: <874lvm52bn.fsf@netris.org> (Mark H. Weaver's message of "Sun, 11 Jun 2017 04:57:32 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> I'm not sure why you think "we are all guilty".  Is it because we have a
> collective responsibility to merge 'staging' more quickly than would be
> possible if we waited for someone to test it first?  If so, I disagree.

Yes, I wrote “we are all guilty” because I think we are collectively
responsible.  Those who worked on it did their best to track and fix
problems on the branch before merging and simply overlooked this
problem; IOW, there was some testing, just not this particular test,
which, in hindsight, is a mistake.

> On the contrary, I believe we have a responsibility to make sure major
> upgrade branches are tested before they are merged, because a broken
> 'master' effectively means that we cannot deploy security updates to
> users until the problem is fixed.

I agree.

But again, the branch was tested.  Remember that gnome-shell is just one
of the many things this branch touched; many other things lower in stack
were upgraded.

IOW, let’s not be too harsh to ourselves.  We made an embarrassing
mistake; we fixed it in a couple of days, and the lesson we learned is
that we must test a full GNOME desktop the next time we upgrade things
in this area.

Ludo’.

  reply	other threads:[~2017-06-11 13:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  4:59 bug#27264: gnome-shell-3.24.2 consistently dies during initialization Mark H Weaver
2017-06-07 10:37 ` Ludovic Courtès
2017-06-07 13:15   ` Roel Janssen
2017-06-07 21:58     ` Mark H Weaver
2017-06-08  6:03       ` Marius Bakke
2017-06-08  6:29         ` Mark H Weaver
2017-06-08 12:35           ` Kei Kebreau
2017-06-08 16:13           ` Marius Bakke
2017-06-08 16:29             ` Marius Bakke
2017-06-09  6:23               ` Chris Marusich
2017-06-09  7:02               ` Mark H Weaver
2017-06-08  7:39         ` Ben Sturmfels
2017-06-08  6:48       ` pelzflorian (Florian Pelz)
2017-06-08 12:01       ` Ludovic Courtès
2017-06-08 12:23         ` Kei Kebreau
2017-06-08 13:09           ` Roel Janssen
2017-06-08 18:08           ` Roel Janssen
2017-06-08 18:34             ` Kei Kebreau
2017-06-08 14:01         ` Mark H Weaver
2017-06-08 14:54           ` Chris Marusich
2017-06-08 17:08           ` Leo Famulari
2017-06-08 17:19             ` Marius Bakke
2017-06-08 17:29             ` Catonano
2017-06-08 17:45               ` Leo Famulari
2017-06-08 18:12             ` Leo Famulari
2017-06-08 20:47           ` Ludovic Courtès
2017-06-11  8:57             ` Mark H Weaver
2017-06-11 13:16               ` Ludovic Courtès [this message]
2017-06-08 14:20         ` pelzflorian (Florian Pelz)

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zidevf5b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27264@debbugs.gnu.org \
    --cc=mhw@netris.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).