GNU bug report logs - #43268
Update Org for Emacs 27.2

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 43268 in the body.
You can then email your comments to 43268 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Update Org for Emacs 27.2
Date: Tue, 08 Sep 2020 07:06:08 +0200

Emacs 27.1 ships with Org 9.3.  Since 2019-12-03T22:27:04Z!bzg <at> gnu.org,
Org's maint branch has collected a few bugfixes for the 9.3 release;
would it make sense to update the emacs-27 branch with Org 9.3.8[1], so
that Emacs 27.2 includes these fixes?

As Stefan suggested in bug#42184, if our maintainers agree, I'll mark
this issue as blocking for bug#43018.


[1] Which I assume will be the final 9.3 release, since 9.4 seems just
    round the corner.

Message #8 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Cc: bzg <at> gnu.org, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Tue, 08 Sep 2020 17:17:18 +0300

> From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
> Date: Tue, 08 Sep 2020 07:06:08 +0200
> Cc: bzg <at> gnu.org
> 
> Emacs 27.1 ships with Org 9.3.  Since 2019-12-03T22:27:04Z!bzg <at> gnu.org,
> Org's maint branch has collected a few bugfixes for the 9.3 release;
> would it make sense to update the emacs-27 branch with Org 9.3.8[1], so
> that Emacs 27.2 includes these fixes?

If the Org developers think it's a good idea, sure.

> As Stefan suggested in bug#42184, if our maintainers agree, I'll mark
> this issue as blocking for bug#43018.

Will you also volunteer to remove the block when Org 9.3 is installed
in the Emacs repository?

Message #11 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: bzg <at> gnu.org, 43268 <at> debbugs.gnu.org,
 Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Tue, 08 Sep 2020 16:46:55 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

Hi Eli,

>> As Stefan suggested in bug#42184, if our maintainers agree, I'll mark
>> this issue as blocking for bug#43018.
>
> Will you also volunteer to remove the block when Org 9.3 is installed
> in the Emacs repository?

Wouldn't it be sufficient if this (bug#43268) is moved to done?

Best regards, Michael.

Message #14 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: bzg <at> gnu.org, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Tue, 08 Sep 2020 17:58:47 +0300

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>,
>   bzg <at> gnu.org,
>   43268 <at> debbugs.gnu.org
> Date: Tue, 08 Sep 2020 16:46:55 +0200
> 
> >> As Stefan suggested in bug#42184, if our maintainers agree, I'll mark
> >> this issue as blocking for bug#43018.
> >
> > Will you also volunteer to remove the block when Org 9.3 is installed
> > in the Emacs repository?
> 
> Wouldn't it be sufficient if this (bug#43268) is moved to done?

It should, but Someone™ should actually do that...

Message #17 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: bzg <at> gnu.org, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Wed, 09 Sep 2020 00:01:29 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
>> Date: Tue, 08 Sep 2020 07:06:08 +0200
>> Cc: bzg <at> gnu.org
>> 
>> Emacs 27.1 ships with Org 9.3.  Since 2019-12-03T22:27:04Z!bzg <at> gnu.org,
>> Org's maint branch has collected a few bugfixes for the 9.3 release;
>> would it make sense to update the emacs-27 branch with Org 9.3.8[1], so
>> that Emacs 27.2 includes these fixes?
>
> If the Org developers think it's a good idea, sure.

Yup, I waited for Bastien's green light before opening this[1].

>> As Stefan suggested in bug#42184, if our maintainers agree, I'll mark
>> this issue as blocking for bug#43018.
>
> Will you also volunteer to remove the block when Org 9.3 is installed
> in the Emacs repository?

I solemnly vow to git fetch emacs.git 𝒮ℴ𝓂ℯ𝓌𝒽𝒶𝓉 ℛℯℊ𝓊𝓁𝒶𝓇𝓁𝓎™ and close this
issue as soon as I see 9.3.8 (or later) landing on emacs-27, in case
no-one beats me to it.

In the unfortunate event that I fail to close this issue in a timely
manner, I fully commit to an off-list message to whoever closed it in my
stead, offering my ℳℴ𝓈𝓉 𝒞ℴ𝓃𝓉𝓇𝒾𝓉ℯ 𝒜𝓅ℴ𝓁ℴℊ𝓎™ for wasting per valuable time.


[1] https://lists.gnu.org/archive/html/emacs-orgmode/2020-09/msg00371.html
    emacs-orgmode <878sdlscpr.fsf <at> gnu.org>

Message #22 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Cc: bzg <at> gnu.org, Eli Zaretskii <eliz <at> gnu.org>, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 23 Nov 2020 15:09:30 -0500

Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:

>>> Emacs 27.1 ships with Org 9.3.  Since 2019-12-03T22:27:04Z!bzg <at> gnu.org,
>>> Org's maint branch has collected a few bugfixes for the 9.3 release;
>>> would it make sense to update the emacs-27 branch with Org 9.3.8[1], so
>>> that Emacs 27.2 includes these fixes?
>>
>> If the Org developers think it's a good idea, sure.
>
> Yup, I waited for Bastien's green light before opening this[1].

What is the status here?

Eli just indicated that we will see a pre-release candidate for version
27.2 very soon.  It would be great to get Org 9.3.8 merged before then.

Message #25 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: bzg <at> gnu.org, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Thu, 26 Nov 2020 18:41:03 +0200

Ping!  Any news?  I'd like to start the pretest of Emacs 27.2 soon.

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Mon, 23 Nov 2020 15:09:30 -0500
> Cc: Eli Zaretskii <eliz <at> gnu.org>, bzg <at> gnu.org, 43268 <at> debbugs.gnu.org
> 
> Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:
> 
> >>> Emacs 27.1 ships with Org 9.3.  Since 2019-12-03T22:27:04Z!bzg <at> gnu.org,
> >>> Org's maint branch has collected a few bugfixes for the 9.3 release;
> >>> would it make sense to update the emacs-27 branch with Org 9.3.8[1], so
> >>> that Emacs 27.2 includes these fixes?
> >>
> >> If the Org developers think it's a good idea, sure.
> >
> > Yup, I waited for Bastien's green light before opening this[1].
> 
> What is the status here?
> 
> Eli just indicated that we will see a pre-release candidate for version
> 27.2 very soon.  It would be great to get Org 9.3.8 merged before then.
> 

Message #28 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Bastien <bzg <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Stefan Kangas <stefan <at> marxist.se>, 43268 <at> debbugs.gnu.org,
 kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Thu, 26 Nov 2020 17:48:19 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> Ping!  Any news?  I'd like to start the pretest of Emacs 27.2 soon.

The latest Org stable version is 9.4 and can safely be included in
Emacs pretest release.

I will probably release 9.4.1 over the week-end to include the latest
fixes made in the last two months.

Using 9.4.1 in the Emacs pretest release is safe too.

-- 
 Bastien

Message #31 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bastien <bzg <at> gnu.org>
Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Thu, 26 Nov 2020 21:17:29 +0200

> From: Bastien <bzg <at> gnu.org>
> Cc: Stefan Kangas <stefan <at> marxist.se>,  kevin.legouguec <at> gmail.com,
>   43268 <at> debbugs.gnu.org
> Date: Thu, 26 Nov 2020 17:48:19 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Ping!  Any news?  I'd like to start the pretest of Emacs 27.2 soon.
> 
> The latest Org stable version is 9.4 and can safely be included in
> Emacs pretest release.
> 
> I will probably release 9.4.1 over the week-end to include the latest
> fixes made in the last two months.
> 
> Using 9.4.1 in the Emacs pretest release is safe too.

Thanks.  I would appreciate if someone could update the Org files in
the Emacs Git repository with whatever version you consider the best
for the Emacs 27.2 release, be it 9.4 or 9.4.1.  Would it be possible
to do that this weekend?

Message #34 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: Bastien <bzg <at> gnu.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Stefan Kangas <stefan <at> marxist.se>,
 Ihor Radchenko <yantar92 <at> gmail.com>, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Thu, 26 Nov 2020 22:41:43 +0100

Bastien <bzg <at> gnu.org> writes:

> I will probably release 9.4.1 over the week-end to include the latest
> fixes made in the last two months.
>
> Using 9.4.1 in the Emacs pretest release is safe too.

Mmm, I can name a few somewhat-disruptive changes in 9.4 that might
throw people off.  For example:

- the new default value for org-startup-folded, as well as some pesky
  side-effects with logbook visibility[1],

- RET and C-j honoring electric-indent-mode (thus bringing Org in line
  with the rest of Emacs), which has caused some uproar on the mailing
  list recently[2].

(And then there's everything under "Incompatible changes" in ORG-NEWS.)

It's not my call of course, but I would argue that if we want 27.2 to be
a no-surprise, bugfix-only release, 9.3.8 would be a safer option.


[1] https://orgmode.org/list/875z83hwuc.fsf <at> gmail.com/
    tl;dr:

    $ wget https://orgmode.org/list/87eepuz0bj.fsf <at> gmail.com/2-logbooks.org
    $ emacs -Q 2-logbooks.org
    C-s bug

    - with Org up to 9.3.8, logbooks remain closed;

    - with Org 9.4, logbooks are opened during the search; this adds a
      lot of clutter and robs the user of a lot of context;
      (can reproduce on maint, 2d23d55ac)

    - this can also be reproduced with Org master, 9a154910e, although I
      could have sworn that Ihor (CC'ed) had committed something to
      address this.

[2] https://orgmode.org/list/2020-11-13T18-23-43 <at> devnull.Karl-Voit.at/t/
    tl;dr:
    Lots of Org users were using RET with electric-indent-mode on,
    unaware that their prose was one TAB away from being indented.  9.4
    made RET honor electric-indent-mode and indents, and much grief
    ensued.
    My (maybe biased) takeway is that the default value of
    org-adapt-indentation should be changed, as evidenced by the
    non-indented reference examples shown on orgmode.org, and the
    .dir-locals.el setting at the root of Org's repo.

Message #37 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Bastien <bzg <at> gnu.org>
To: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Stefan Kangas <stefan <at> marxist.se>,
 Ihor Radchenko <yantar92 <at> gmail.com>, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Thu, 26 Nov 2020 23:49:36 +0100

Hi Kévin,

Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:

> Mmm, I can name a few somewhat-disruptive changes in 9.4 that might
> throw people off.  For example:
>
> - the new default value for org-startup-folded, as well as some pesky
>   side-effects with logbook visibility[1],

this looks like a bug that needs to be fixed, I will have a look this
week-end.

> - RET and C-j honoring electric-indent-mode (thus bringing Org in line
>   with the rest of Emacs), which has caused some uproar on the mailing
>   list recently[2].

If it makes Org more consistent with other Emacs modes, it looks like
a good change, so I would not discard this one.

> (And then there's everything under "Incompatible changes" in
> ORG-NEWS.)

I don't see anything problematic here.

> It's not my call of course, but I would argue that if we want 27.2 to be
> a no-surprise, bugfix-only release, 9.3.8 would be a safer option.

I think merging Org 9.4.x into Emacs 27.2 is a good way to propagate
latest Org changes, I'm not sure they qualify as "surprising" changes,
but I won't argue.

-- 
 Bastien

Message #40 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Bastien <bzg <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Thu, 26 Nov 2020 23:49:56 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> Thanks.  I would appreciate if someone could update the Org files in
> the Emacs Git repository with whatever version you consider the best
> for the Emacs 27.2 release, be it 9.4 or 9.4.1.  Would it be possible
> to do that this weekend?

Yes, I will do this, thanks!

-- 
 Bastien

Message #43 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bastien <bzg <at> gnu.org>
Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Wed, 02 Dec 2020 17:10:14 +0200

> From: Bastien <bzg <at> gnu.org>
> Cc: stefan <at> marxist.se,  kevin.legouguec <at> gmail.com,  43268 <at> debbugs.gnu.org
> Date: Thu, 26 Nov 2020 23:49:56 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Thanks.  I would appreciate if someone could update the Org files in
> > the Emacs Git repository with whatever version you consider the best
> > for the Emacs 27.2 release, be it 9.4 or 9.4.1.  Would it be possible
> > to do that this weekend?
> 
> Yes, I will do this, thanks!

Ping!  Any news with this?

Message #46 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: bzg <at> gnu.org
Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Tue, 08 Dec 2020 17:11:22 +0200

Ping! Ping!  Please update Org on the emacs-27 branch soon.  If I see
no progress with this within the next couple of days, I will
reluctantly begin preparing the Emacs 27.2 pretest with the version we
have now.

> Date: Wed, 02 Dec 2020 17:10:14 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
> 
> > From: Bastien <bzg <at> gnu.org>
> > Cc: stefan <at> marxist.se,  kevin.legouguec <at> gmail.com,  43268 <at> debbugs.gnu.org
> > Date: Thu, 26 Nov 2020 23:49:56 +0100
> > 
> > Eli Zaretskii <eliz <at> gnu.org> writes:
> > 
> > > Thanks.  I would appreciate if someone could update the Org files in
> > > the Emacs Git repository with whatever version you consider the best
> > > for the Emacs 27.2 release, be it 9.4 or 9.4.1.  Would it be possible
> > > to do that this weekend?
> > 
> > Yes, I will do this, thanks!
> 
> Ping!  Any news with this?

Message #49 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Bastien <bzg <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Tue, 08 Dec 2020 16:35:25 +0100

Hi Eli,

sorry, I was snowed under my job tasks, I will proceed ASAP.

Eli Zaretskii <eliz <at> gnu.org> writes:

> Ping! Ping!  Please update Org on the emacs-27 branch soon.  If I see
> no progress with this within the next couple of days, I will
> reluctantly begin preparing the Emacs 27.2 pretest with the version we
> have now.

-- 
 Bastien

Message #52 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bastien <bzg <at> gnu.org>
Cc: stefan <at> marxist.se, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Tue, 08 Dec 2020 19:01:43 +0200

> From: Bastien <bzg <at> gnu.org>
> Cc: stefan <at> marxist.se,  43268 <at> debbugs.gnu.org,  kevin.legouguec <at> gmail.com
> Date: Tue, 08 Dec 2020 16:35:25 +0100
> 
> Hi Eli,
> 
> sorry, I was snowed under my job tasks, I will proceed ASAP.

Thank you.

Message #57 received at 43268-done <at> debbugs.gnu.org (full text, mbox):

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Bastien <bzg <at> gnu.org>, stefan <at> marxist.se, 43268-done <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Sun, 13 Dec 2020 22:12:57 +0100

With 2020-12-13 "Update to Org 9.4.1" (f22856a5c5), Org has been updated
on the emacs-27 branch.  I'm therefore closing this.

Thank you Bastien! 🙏

Message #60 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Sun, 13 Dec 2020 22:34:15 +0100

Michael Albinus <michael.albinus <at> gmx.de> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>> Will you also volunteer to remove the block when Org 9.3 is installed
>> in the Emacs repository?
>
> Wouldn't it be sufficient if this (bug#43268) is moved to done?

About that…

Closing this bug seems to have removed it from the list shown at the top
of https://debbugs.gnu.org/43018 ("Fixed blocked by"); however, it's
still present on M-x debbugs-gnu-emacs-release-blocking-reports (like
42851).

1. Do we care?
2. If so,
    a. should I tell debbugs to "unblock 43018 by 43268"?
    b. should we teach debbugs.el to ignore closed bugs when listing
       blockers?

Message #63 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Lars Ingebrigtsen <larsi <at> gnus.org>,
 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 08:50:43 +0100

Kévin Le Gouguec <kevin.legouguec <at> gmail.com> writes:

Hi Kévin,

>>> Will you also volunteer to remove the block when Org 9.3 is installed
>>> in the Emacs repository?
>>
>> Wouldn't it be sufficient if this (bug#43268) is moved to done?
>
> About that…
>
> Closing this bug seems to have removed it from the list shown at the top
> of https://debbugs.gnu.org/43018 ("Fixed blocked by"); however, it's
> still present on M-x debbugs-gnu-emacs-release-blocking-reports (like
> 42851).

Yes, but it is marked as done.

> 1. Do we care?
> 2. If so,
>     a. should I tell debbugs to "unblock 43018 by 43268"?
>     b. should we teach debbugs.el to ignore closed bugs when listing
>        blockers?

There are different approaches. I, for example, believe the bug can be
kept in the list. Other people prefer to remove it.

Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
show only the open bugs.

Eli? Lars?

Best regards, Michael.

Message #66 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Cc: michael.albinus <at> gmx.de, 43268 <at> debbugs.gnu.org
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 17:27:48 +0200

> From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  43268 <at> debbugs.gnu.org
> Date: Sun, 13 Dec 2020 22:34:15 +0100
> 
> Closing this bug seems to have removed it from the list shown at the top
> of https://debbugs.gnu.org/43018 ("Fixed blocked by"); however, it's
> still present on M-x debbugs-gnu-emacs-release-blocking-reports (like
> 42851).
> 
> 1. Do we care?

Only if you look at the results of that command (I don't).

> 2. If so,
>     a. should I tell debbugs to "unblock 43018 by 43268"?

That'd be incorrect, because the bug could be reopened.

>     b. should we teach debbugs.el to ignore closed bugs when listing
>        blockers?

Why bother?

Message #69 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: larsi <at> gnus.org, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 17:41:03 +0200

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  43268 <at> debbugs.gnu.org, Lars Ingebrigtsen
>  <larsi <at> gnus.org>
> Date: Mon, 14 Dec 2020 08:50:43 +0100
> 
> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
> show only the open bugs.

It could be useful to have an indication that it's closed, but I
wouldn't remove them nor hide them.

Message #72 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 43268 <at> debbugs.gnu.org,
 Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 16:47:10 +0100

Michael Albinus <michael.albinus <at> gmx.de> writes:

> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
> show only the open bugs.
>
> Eli? Lars?

I think I vaguely prefer having it list all the (unarchived) blocker
bugs?  Then you can watch the number of closed blocker bugs grow, which
seems satisfying.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #75 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: larsi <at> gnus.org, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 16:55:36 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
>> show only the open bugs.
>
> It could be useful to have an indication that it's closed, but I
> wouldn't remove them nor hide them.

There is an indication. The list shows the "done" tag, and it has
another face.

Best regards, Michael.

Message #78 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 43268 <at> debbugs.gnu.org,
 Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 16:56:43 +0100

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

>> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
>> show only the open bugs.
>>
>> Eli? Lars?
>
> I think I vaguely prefer having it list all the (unarchived) blocker
> bugs?  Then you can watch the number of closed blocker bugs grow, which
> seems satisfying.  :-)

So I'll change nothing. Seeing archived bugs is even more satifying.

Best regards, Michael.

Message #81 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: larsi <at> gnus.org, 43268 <at> debbugs.gnu.org, kevin.legouguec <at> gmail.com
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 18:45:54 +0200

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: kevin.legouguec <at> gmail.com,  43268 <at> debbugs.gnu.org,  larsi <at> gnus.org
> Date: Mon, 14 Dec 2020 16:55:36 +0100
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
> >> show only the open bugs.
> >
> > It could be useful to have an indication that it's closed, but I
> > wouldn't remove them nor hide them.
> 
> There is an indication. The list shows the "done" tag, and it has
> another face.

Then I don't think I see a problem, thanks.

Message #84 received at 43268 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 43268 <at> debbugs.gnu.org,
 Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
Subject: Re: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 19:44:17 +0100

Michael Albinus <michael.albinus <at> gmx.de> writes:

>> I think I vaguely prefer having it list all the (unarchived) blocker
>> bugs?  Then you can watch the number of closed blocker bugs grow, which
>> seems satisfying.  :-)
>
> So I'll change nothing. Seeing archived bugs is even more satifying.

PS: In the bugs list, one can always hide closed / archived bugs by "M-x
debbugs-gnu-toggle-suppress" (bound to "x"). This gives also the desired
effect, if one wants to hide those bugs.

Best regards, Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.