* Handling bugs in obsolete code (was: bug#1452: ...) [not found] ` <CAM6wYYLmXxb7g0f6Xg6D4zRCgUdt-CdXSLPm7LH5AkoDRiKokg@mail.gmail.com> @ 2016-01-07 1:58 ` John Wiegley 2016-01-07 3:27 ` Handling bugs in obsolete code Andrew Hyatt 2016-01-07 7:59 ` Glenn Morris 0 siblings, 2 replies; 7+ messages in thread From: John Wiegley @ 2016-01-07 1:58 UTC (permalink / raw) To: Andrew Hyatt; +Cc: rgm, Eli Zaretskii, hanche, emacs-devel >>>>> 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? -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Handling bugs in obsolete code 2016-01-07 1:58 ` Handling bugs in obsolete code (was: bug#1452: ...) John Wiegley @ 2016-01-07 3:27 ` Andrew Hyatt 2016-01-07 6:03 ` John Wiegley 2016-01-07 7:59 ` Glenn Morris 1 sibling, 1 reply; 7+ messages in thread From: Andrew Hyatt @ 2016-01-07 3:27 UTC (permalink / raw) To: Eli Zaretskii; +Cc: rgm, hanche, emacs-devel 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. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Handling bugs in obsolete code 2016-01-07 3:27 ` Handling bugs in obsolete code Andrew Hyatt @ 2016-01-07 6:03 ` John Wiegley 0 siblings, 0 replies; 7+ messages in thread From: John Wiegley @ 2016-01-07 6:03 UTC (permalink / raw) To: Andrew Hyatt; +Cc: rgm, Eli Zaretskii, hanche, emacs-devel >>>>> Andrew Hyatt <ahyatt@gmail.com> writes: > 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. If minor is currently be filtered, it should be possible to filter obsolete as well. > 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. The advantage to having obsolete is that it would make it easier to find the bugs we need to close whenever obsolete code is being deleted. -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Handling bugs in obsolete code 2016-01-07 1:58 ` Handling bugs in obsolete code (was: bug#1452: ...) John Wiegley 2016-01-07 3:27 ` Handling bugs in obsolete code Andrew Hyatt @ 2016-01-07 7:59 ` Glenn Morris 2016-01-07 8:28 ` CHENG Gao 2016-01-07 16:10 ` Eli Zaretskii 1 sibling, 2 replies; 7+ messages in thread From: Glenn Morris @ 2016-01-07 7:59 UTC (permalink / raw) To: emacs-devel; +Cc: Eli Zaretskii, Andrew Hyatt I think you're over-thinking it. The number of bugs in "obsolete" files is a tiny, insignificant fraction, and always will be. (I'm not even sure there are any left open.) Their influence on your stats will not be measurable. As debbugs.gnu.org maintainer, I won't define a new global "obsolete" tag for such a minority use. You could use a usertag, if you really want to (or just retitle them to add eg "[obsolete]"). ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Handling bugs in obsolete code 2016-01-07 7:59 ` Glenn Morris @ 2016-01-07 8:28 ` CHENG Gao 2016-01-07 16:10 ` Eli Zaretskii 1 sibling, 0 replies; 7+ messages in thread From: CHENG Gao @ 2016-01-07 8:28 UTC (permalink / raw) To: emacs-devel Many files were put into obsolete/ dir for long time, since 22.1 or 23.1. It does not make sense to continue keeping them there. But it's just MPO. How about some policy to handle this? Say keep version-1 or version-2. For one last time, keep them all in 25.1 release tarball, and then delete all except "Obsolete-since: 25.1/24.5", and then roll like this. If anyone needs, they can pull from 25.1 tarball. And maybe add instruction to each file, something like superceded-by etc. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Handling bugs in obsolete code 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 1 sibling, 1 reply; 7+ messages in thread From: Eli Zaretskii @ 2016-01-07 16:10 UTC (permalink / raw) To: Glenn Morris; +Cc: ahyatt, emacs-devel > From: Glenn Morris <rgm@gnu.org> > Cc: Eli Zaretskii <eliz@gnu.org>, Andrew Hyatt <ahyatt@gmail.com> > Date: Thu, 07 Jan 2016 02:59:32 -0500 > > I think you're over-thinking it. > The number of bugs in "obsolete" files is a tiny, insignificant > fraction, and always will be. (I'm not even sure there are any left open.) > Their influence on your stats will not be measurable. > > As debbugs.gnu.org maintainer, I won't define a new global "obsolete" > tag for such a minority use. You could use a usertag, if you really want > to (or just retitle them to add eg "[obsolete]"). Retitling sounds right to me, FWIW. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Handling bugs in obsolete code 2016-01-07 16:10 ` Eli Zaretskii @ 2016-01-07 18:17 ` John Wiegley 0 siblings, 0 replies; 7+ messages in thread From: John Wiegley @ 2016-01-07 18:17 UTC (permalink / raw) To: Eli Zaretskii; +Cc: Glenn Morris, ahyatt, emacs-devel >>>>> Eli Zaretskii <eliz@gnu.org> writes: >> As debbugs.gnu.org maintainer, I won't define a new global "obsolete" tag >> for such a minority use. You could use a usertag, if you really want to (or >> just retitle them to add eg "[obsolete]"). > Retitling sounds right to me, FWIW. Yes, retitling sounds good. -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-01-07 18:17 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <20081129.145347.35808910.hanche@math.ntnu.no> [not found] ` <handler.1452.B.122796683914175.ack@emacsbugs.donarmstrong.com> [not found] ` <20081129.155222.124907962.hanche@math.ntnu.no> [not found] ` <20081129.161126.71259916.hanche@math.ntnu.no> [not found] ` <m2h9issm28.fsf@Andrews-MacBook-Pro.local.i-did-not-set--mail-host-address--so-tickle-me> [not found] ` <5vy4c46ifr.fsf@fencepost.gnu.org> [not found] ` <83oacz5188.fsf@gnu.org> [not found] ` <m27fjnwymn.fsf@newartisans.com> [not found] ` <CAM6wYYJ+bfDuyF1aJDJERJTzXUrqMjOiOwtdbGPWRSbuE-3+EQ@mail.gmail.com> [not found] ` <83y4c32wwf.fsf@gnu.org> [not found] ` <CAM6wYYLmXxb7g0f6Xg6D4zRCgUdt-CdXSLPm7LH5AkoDRiKokg@mail.gmail.com> 2016-01-07 1:58 ` Handling bugs in obsolete code (was: bug#1452: ...) John Wiegley 2016-01-07 3:27 ` Handling bugs in obsolete code Andrew Hyatt 2016-01-07 6:03 ` 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
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs.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).