all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrew Hyatt <ahyatt@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, hanche@math.ntnu.no, emacs-devel@gnu.org
Subject: Re: Handling bugs in obsolete code
Date: Wed, 06 Jan 2016 22:27:30 -0500	[thread overview]
Message-ID: <m2wprmqdb1.fsf@gmail.com> (raw)
In-Reply-To: <m237ua2ls6.fsf_-_@newartisans.com> (John Wiegley's message of "Wed, 06 Jan 2016 17:58:17 -0800")

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> Andrew Hyatt <ahyatt@gmail.com> writes:
>
>> On Tue, Jan 5, 2016 at 10:46 PM Eli Zaretskii <eliz@gnu.org> wrote:
>>> From: Andrew Hyatt <ahyatt@gmail.com>
>>> 
>>> Has anyone considered putting these obsolete packages in the gnu ELPA? I'm
>>> not sure about the bug policy, but I'd guess that bugs shouldn't be filed
>>> against ELPA packages.
>
>>     AFAIK bugs are files against ELPA packages like they are against the
>>     core Emacs. So moving to ELPA will not change this aspect of obsolete
>>     packages.
>
>>     (It also feels wrong to move them to ELPA just because they are
>>     obsolete. ELPA is supposed to be home for new and advanced stuff, not
>>     for obsolete stuff. If someone steps forward wanting to maintain an
>>     obsolete package, then a move to ELPA might make good sense, though.)
>
>> That's a fair point. Maybe there could be some special ELPA repository for
>> obsolete packages. But what I'm mostly trying to figure out is if there is
>> *any* way to get code to be completely unmaintained. We are, after all,
>> trying to reduce the number of bugs (see the thread on 4k bugs) overall, and
>> this is one way to do that. So the only way people would agree on right now,
>> is if we remove the code entirely from emacs distribution. But I suspect
>> that such a change would be rejected, even from obsolete packages, because
>> someone might still be depending on them.
>
> What if we just use an "obsolete" tag, so the bugs could be filtered out from
> our running total, but they still remain open?

That would help, although it would still mean that new bugs would have
to be triaged and tagged as obsolete, as opposed to not existing at all.
If we did such a thing, it'd be nice if debbugs filtered obsolete tags
by default.

Another variant on that is to say that all bugs against obsolete packages
have "minor" severity, which would accomplish the same thing without
needing a new tag.  On the hopefully rare occasions in which the bug
really is severe (crashes emacs, corrupts data, etc) it can be have a
non-minor severity.



  reply	other threads:[~2016-01-07  3:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 13:53 bug#1452: 23.0.60; Problem with nextstep, longlines-mode, Harald Hanche-Olsen
     [not found] ` <handler.1452.B.122796683914175.ack@emacsbugs.donarmstrong.com>
2008-11-29 14:52   ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Harald Hanche-Olsen
2008-11-29 15:11     ` Harald Hanche-Olsen
2016-01-05  4:10       ` Andrew Hyatt
2016-01-05 17:32         ` Glenn Morris
2016-01-05 17:39           ` Andrew Hyatt
2016-01-05 17:53             ` Harald Hanche-Olsen
2016-01-05 18:38             ` Eli Zaretskii
2016-01-05 18:29           ` Eli Zaretskii
2016-01-05 20:38             ` John Wiegley
2016-01-05 20:46               ` Eli Zaretskii
2016-01-05 21:15                 ` Harald Hanche-Olsen
2016-01-05 21:12               ` Andrew Hyatt
2016-01-05 21:34                 ` John Wiegley
2016-01-05 21:50                   ` Dmitry Gutov
2016-01-06  1:47                     ` Andrew Hyatt
2016-01-06  1:53                       ` Dmitry Gutov
2016-01-06  3:45                 ` Eli Zaretskii
2016-01-07  1:42                   ` Andrew Hyatt
2016-01-07  1:58                     ` Handling bugs in obsolete code (was: bug#1452: ...) John Wiegley
2016-01-07  3:27                       ` Andrew Hyatt [this message]
2016-01-07  6:03                         ` Handling bugs in obsolete code John Wiegley
2016-01-07  7:59                       ` Glenn Morris
2016-01-07  8:28                         ` CHENG Gao
2016-01-07 16:10                         ` Eli Zaretskii
2016-01-07 18:17                           ` John Wiegley
2016-01-07  3:42                     ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Eli Zaretskii
2016-01-07  3:54                       ` Andrew Hyatt
2016-01-07 16:02                         ` Eli Zaretskii
2016-01-06  8:28                 ` Xue Fuqiao
2016-01-06 18:16                   ` Glenn Morris

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=m2wprmqdb1.fsf@gmail.com \
    --to=ahyatt@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=hanche@math.ntnu.no \
    --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.