[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#39200: Release 27.1
From: |
Eli Zaretskii |
Subject: |
bug#39200: Release 27.1 |
Date: |
Sun, 23 Aug 2020 22:01:11 +0300 |
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Stefan Kangas <stefan@marxist.se>, 39200@debbugs.gnu.org
> Date: Sun, 23 Aug 2020 20:57:42 +0200
>
> > We didn't miss them. I decided they weren't important enough to hold
> > the release.
>
> That's pretty OK as maintainer decision. But shouldn't the two bugs then
> be removed from blocking ones for bug#39200? At least a communication
> about this decision I have missed, perhaps because I didn't see it.
Some people react emotionally when I close bugs against their
opinions, so I sometimes decide not to do that.
> And should the two bugs now be marked as blocking for 27.2.?
I don't mind, but if the motivation for fixing them will remain as it
was until now, they will probably be ignored for 27.2 as well. it is
hard to treat seriously a bug report that no one feels motivated
enough to work on.
- bug#39200: Release 27.1, Stefan Kangas, 2020/08/23
- bug#39200: Release 27.1, Michael Albinus, 2020/08/23
- bug#39200: Release 27.1, Eli Zaretskii, 2020/08/23
- bug#39200: Release 27.1, Michael Albinus, 2020/08/23
- bug#39200: Release 27.1,
Eli Zaretskii <=
- bug#39200: Release 27.1, Michael Albinus, 2020/08/23
- bug#39200: Release 27.1, Eli Zaretskii, 2020/08/23
- bug#39200: Release 27.1, Michael Albinus, 2020/08/23
- bug#39200: Release 27.1, Eli Zaretskii, 2020/08/23
- bug#39200: Release 27.1, Michael Albinus, 2020/08/24
- bug#39200: Release 27.1, Eli Zaretskii, 2020/08/24
- bug#39200: Release 27.1, Michael Albinus, 2020/08/24
- bug#39200: Release 27.1, Dmitry Gutov, 2020/08/23
- bug#39200: Release 27.1, Eli Zaretskii, 2020/08/24
bug#39200: Release 27.1, Stefan Kangas, 2020/08/23