GNU bug report logs -
#39200
Release 27.1
Previous Next
Reported by: Michael Albinus <michael.albinus <at> gmx.de>
Date: Mon, 20 Jan 2020 12:15:01 UTC
Severity: normal
Tags: fixed
Fixed in version 27.1
Done: Michael Albinus <michael.albinus <at> gmx.de>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 39200 in the body.
You can then email your comments to 39200 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Acknowledgement sent
to
Michael Albinus <michael.albinus <at> gmx.de>
:
New bug report received and filed, but not forwarded.
(Mon, 20 Jan 2020 12:15:01 GMT)
Full text and
rfc822 format available.
Message #3 received at quiet <at> debbugs.gnu.org (full text, mbox):
Package: emacs
Version: 27.1
Severity: normal
Added blocking bug(s) 39187
Request was from
Michael Albinus <michael.albinus <at> gmx.de>
to
control <at> debbugs.gnu.org
.
(Mon, 20 Jan 2020 12:32:02 GMT)
Full text and
rfc822 format available.
Added blocking bug(s) 36006
Request was from
Noam Postavsky <npostavs <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Thu, 27 Feb 2020 13:17:01 GMT)
Full text and
rfc822 format available.
Added blocking bug(s) 40247
Request was from
Eli Zaretskii <eliz <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 27 Mar 2020 07:13:02 GMT)
Full text and
rfc822 format available.
Added blocking bug(s) 40248
Request was from
Eli Zaretskii <eliz <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 27 Mar 2020 07:15:02 GMT)
Full text and
rfc822 format available.
Removed blocking bug(s) 40248
Request was from
Eli Zaretskii <eliz <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 03 Apr 2020 11:36:02 GMT)
Full text and
rfc822 format available.
Added blocking bug(s) 41423
Request was from
Michael Albinus <michael.albinus <at> gmx.de>
to
control <at> debbugs.gnu.org
.
(Thu, 28 May 2020 11:53:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 13:27:01 GMT)
Full text and
rfc822 format available.
Message #18 received at 39200 <at> debbugs.gnu.org (full text, mbox):
help-debbugs <at> gnu.org (GNU bug Tracking System) writes:
> Thank you for filing a new bug report with debbugs.gnu.org.
Seems like there are two blocking bugs here that were marked as blocking
release 27.1:
41423: 27.0.91; eshell file completion in tramp dir is slow (3 minutes)
[regression on pretest]
36006: electric-pair-mode fails to balance in certain cases
It doesn't seem ideal that we missed these outstanding and presumably
release critical bugs. Maybe someone should clean this up, and think
about how we should use bugs like this in the future.
Best regards,
Stefan Kangas
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 17:17:02 GMT)
Full text and
rfc822 format available.
Message #21 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefan <at> marxist.se> writes:
Hi Stefan,
>> Thank you for filing a new bug report with debbugs.gnu.org.
>
> Seems like there are two blocking bugs here that were marked as blocking
> release 27.1:
>
> 41423: 27.0.91; eshell file completion in tramp dir is slow (3 minutes)
> [regression on pretest]
>
> 36006: electric-pair-mode fails to balance in certain cases
>
> It doesn't seem ideal that we missed these outstanding and presumably
> release critical bugs. Maybe someone should clean this up, and think
> about how we should use bugs like this in the future.
We still have no established and accepted method how to keep
must-to-be-fixed bugs. In fact, it depends mainly on the Emacs
maintainer(s) what to apply.
> Best regards,
> Stefan Kangas
Best regards, Michael.
Changed bug title to 'Release 27.2' from 'Release 27.1'
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Sun, 23 Aug 2020 17:56:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 18:46:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 39200 <at> debbugs.gnu.org (full text, mbox):
> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Sun, 23 Aug 2020 09:26:12 -0400
> Cc: 39200 <at> debbugs.gnu.org
>
> Seems like there are two blocking bugs here that were marked as blocking
> release 27.1:
>
> 41423: 27.0.91; eshell file completion in tramp dir is slow (3 minutes)
> [regression on pretest]
>
> 36006: electric-pair-mode fails to balance in certain cases
>
> It doesn't seem ideal that we missed these outstanding and presumably
> release critical bugs.
We didn't miss them. I decided they weren't important enough to hold
the release.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 18:58:01 GMT)
Full text and
rfc822 format available.
Message #29 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> Seems like there are two blocking bugs here that were marked as blocking
>> release 27.1:
>>
>> 41423: 27.0.91; eshell file completion in tramp dir is slow (3 minutes)
>> [regression on pretest]
>>
>> 36006: electric-pair-mode fails to balance in certain cases
>>
>> It doesn't seem ideal that we missed these outstanding and presumably
>> release critical bugs.
>
> 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.
And should the two bugs now be marked as blocking for 27.2.?
(Sorry to bother you, but I feel like at home: my wife also expects from
me to read her mind and to do proper action, but I fail miserably)
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:02:01 GMT)
Full text and
rfc822 format available.
Message #32 received at 39200 <at> debbugs.gnu.org (full text, mbox):
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Stefan Kangas <stefan <at> marxist.se>, 39200 <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:07:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> We didn't miss them. I decided they weren't important enough to hold
> the release.
OK, sounds good, and thanks for clarifying.
I've now renamed this bug to "Release 27.2". I hope that makes sense
and is somehow helpful for you in preparing the next release.
Perhaps some other adjustments should be made here; some of the blocking
bugs might not be important enough to block 27.2 either, for example.
Best regards,
Stefan Kangas
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:11:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
Hi Eli,
>> 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.
Agreed.
OTOH, it wasn't propagated prominently, that there is a list of
to-be-solved-for-relase bugs. Not so many people know how to see this
list. And maybe we shall send (weekly?) reminder messages with these bug
ids to the emacs-devel ML. WDYT?
Best regards, Michael-
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:14:02 GMT)
Full text and
rfc822 format available.
Message #41 received at 39200 <at> debbugs.gnu.org (full text, mbox):
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: stefan <at> marxist.se, 39200 <at> debbugs.gnu.org
> Date: Sun, 23 Aug 2020 21:10:21 +0200
>
> OTOH, it wasn't propagated prominently, that there is a list of
> to-be-solved-for-relase bugs. Not so many people know how to see this
> list. And maybe we shall send (weekly?) reminder messages with these bug
> ids to the emacs-devel ML. WDYT?
I don't mind, although weekly sounds too frequently.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:19:01 GMT)
Full text and
rfc822 format available.
Message #44 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefan <at> marxist.se> writes:
> I've now renamed this bug to "Release 27.2". I hope that makes sense
> and is somehow helpful for you in preparing the next release.
No, pls revert this renaming. I will create a new bug for 27.2, and I
will update the debbugs package. Likely by tomorrow. (If you beat me -
the better)
If we don't distinguish between releases, there are good chances people
get confused.
> Perhaps some other adjustments should be made here; some of the blocking
> bugs might not be important enough to block 27.2 either, for example.
Yes, perhaps. Unfortunately, nobody feels even responsible to keep this
list of blocking bugs up-to-date.
> Best regards,
> Stefan Kangas
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:24:01 GMT)
Full text and
rfc822 format available.
Message #47 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> OTOH, it wasn't propagated prominently, that there is a list of
>> to-be-solved-for-relase bugs. Not so many people know how to see this
>> list. And maybe we shall send (weekly?) reminder messages with these bug
>> ids to the emacs-devel ML. WDYT?
>
> I don't mind, although weekly sounds too frequently.
Let's say monthly, and weekly once the pretest has started?
I could add a script to the debbugs package, which will do the dirty
steps collecting data and preparing the message. Activation shall still
be performed manually, by whomever feels ready.
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:44:02 GMT)
Full text and
rfc822 format available.
Message #50 received at 39200 <at> debbugs.gnu.org (full text, mbox):
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: stefan <at> marxist.se, 39200 <at> debbugs.gnu.org
> Date: Sun, 23 Aug 2020 21:23:37 +0200
>
> Let's say monthly, and weekly once the pretest has started?
>
> I could add a script to the debbugs package, which will do the dirty
> steps collecting data and preparing the message. Activation shall still
> be performed manually, by whomever feels ready.
Fine with me, thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 19:58:02 GMT)
Full text and
rfc822 format available.
Message #53 received at 39200 <at> debbugs.gnu.org (full text, mbox):
retitle 39200 Release 27.1
thanks
Michael Albinus <michael.albinus <at> gmx.de> writes:
>> I've now renamed this bug to "Release 27.2".
>
> No, pls revert this renaming.
[...]
> If we don't distinguish between releases, there are good chances people
> get confused.
Good point, done.
Best regards,
Stefan Kangas
Changed bug title to 'Release 27.1' from 'Release 27.2'
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Sun, 23 Aug 2020 19:58:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 22:59:02 GMT)
Full text and
rfc822 format available.
Message #58 received at 39200 <at> debbugs.gnu.org (full text, mbox):
On 23.08.2020 22:01, Eli Zaretskii wrote:
>>> 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.
I believe the suggestion was to remove them from blockers, not closing
them. If anyone objects to that, they would object to making a release
before the bugs as fixed as well.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Sun, 23 Aug 2020 23:07:02 GMT)
Full text and
rfc822 format available.
Message #61 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefan <at> marxist.se> writes:
> 36006: electric-pair-mode fails to balance in certain cases
>
> It doesn't seem ideal that we missed these outstanding and presumably
> release critical bugs. Maybe someone should clean this up, and think
> about how we should use bugs like this in the future.
I added 36006 as a blocker because it's a regression, but I wouldn't
call it release critical. I did intend to look at it before release,
but I haven't spent much time on Emacs development recently, for various
reasons.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Mon, 24 Aug 2020 05:00:02 GMT)
Full text and
rfc822 format available.
Message #64 received at 39200 <at> debbugs.gnu.org (full text, mbox):
> Cc: stefan <at> marxist.se, 39200 <at> debbugs.gnu.org
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> Date: Mon, 24 Aug 2020 01:58:21 +0300
>
> On 23.08.2020 22:01, Eli Zaretskii wrote:
> >>> 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.
>
> I believe the suggestion was to remove them from blockers, not closing
> them.
Same issue here.
Added tag(s) fixed.
Request was from
Michael Albinus <michael.albinus <at> gmx.de>
to
control <at> debbugs.gnu.org
.
(Mon, 24 Aug 2020 11:19:02 GMT)
Full text and
rfc822 format available.
bug marked as fixed in version 27.1, send any further explanations to
39200 <at> debbugs.gnu.org and Michael Albinus <michael.albinus <at> gmx.de>
Request was from
Michael Albinus <michael.albinus <at> gmx.de>
to
control <at> debbugs.gnu.org
.
(Mon, 24 Aug 2020 11:19:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Mon, 24 Aug 2020 16:07:01 GMT)
Full text and
rfc822 format available.
Message #71 received at 39200 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Eli Zaretskii <eliz <at> gnu.org> writes:
>> I could add a script to the debbugs package, which will do the dirty
>> steps collecting data and preparing the message. Activation shall still
>> be performed manually, by whomever feels ready.
>
> Fine with me, thanks.
Finally, I've added the command `reminder-for-release-critical-bugs' to
admin/admin.el of the emacs-27 branch. See appended patch.
Comments, especially about the wording of the message, are welcome.
Best regards, Michael.
[Message part 2 (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Mon, 24 Aug 2020 16:13:01 GMT)
Full text and
rfc822 format available.
Message #74 received at 39200 <at> debbugs.gnu.org (full text, mbox):
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: stefan <at> marxist.se, 39200 <at> debbugs.gnu.org
> Date: Mon, 24 Aug 2020 18:05:53 +0200
>
> Finally, I've added the command `reminder-for-release-critical-bugs' to
> admin/admin.el of the emacs-27 branch. See appended patch.
>
> Comments, especially about the wording of the message, are welcome.
I think someone already said those are not necessarily "critical".
How about "release-blocking" instead?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#39200
; Package
emacs
.
(Mon, 24 Aug 2020 16:16:02 GMT)
Full text and
rfc822 format available.
Message #77 received at 39200 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> Finally, I've added the command `reminder-for-release-critical-bugs' to
>> admin/admin.el of the emacs-27 branch. See appended patch.
>>
>> Comments, especially about the wording of the message, are welcome.
>
> I think someone already said those are not necessarily "critical".
> How about "release-blocking" instead?
I'll change.
Best regards, Michael.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 22 Sep 2020 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 213 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.