Date: Mon, 13 Apr 1998 01:13:02 -0300 (ADT) From: The Hermit Hacker <scrappy@hub.org> To: Chuck Robey <chuckr@glue.umd.edu> Cc: Nate Williams <nate@mt.sri.com>, Poul-Henning Kamp <phk@FreeBSD.ORG>, committers@FreeBSD.ORG Subject: Re: IMPORTANT: PRs in suspended state Message-ID: <Pine.BSF.3.96.980413005345.306D-100000@thelab.hub.org> In-Reply-To: <Pine.BSF.3.96.980412214905.410S-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Apr 1998, Chuck Robey wrote:
> On Sun, 12 Apr 1998, Nate Williams wrote:
>
> > Poul-Henning Kamp writes:
> > > In an attempt to get to the 3.0-RELEASE ready frame of mind, I am
> > > doing a end-to-other review of our Gnats database right now. The
> > > PRs which contain substance, but with little or no hope to get done
> > > will be moved to "suspended" state.
> >
> > This seems silly to me, and makes us look even less professional. There
> > is no difference between 'open' and 'suspended' at all. Putting a PR in
> > suspended state is essentially the same as deleting it.
> >
> > Also, a few PR's were closed with "it ain't gonna get fixed", which is
> > just plain stupid. Just because it isn't going to fixed before 3.0
> > doesn't mean it's isn't going to get fixed ever. The point of having a
> > PR database is to have a record of those outstanding bugs that will get
> > fixed.
>
> Do you have a suggestionj as to what to do with PRs that haven't
> anything to do with software that is part of the FreeBSD tree? I'm
> specifically referring to the PRs on ports stuff, where the complaint
> isn't about the port per se, but about the operation of the software
> that the port correctly installs. Such things are, IMO, even more
> unprofessional, because they *can't* be fixed ... no method of closing
> such PRs. It seemed to me that putting things in the suspend state was
> a nice compromise.
I have to disagree here...there comes a point when a PR is
out-dated and irrelevant. Hell, just scanning through a few randomly
shows up:
From: Heikki Suonsivu <hsu@clinet.fi>
To: freebsd-gnats-submit@freebsd.org
Cc: hsu@clinet.fi
Subject: kern/1098 File system corruption (2 cases)
Date: Sat, 28 Mar 1998 04:33:44 +0200 (EET)
fsck has been patched since this, so I am not quite sure if this
any more exists. I haven't seen it for long time, so I think this
can be closed.
The person that submitted the problem report acknowledges that it
can be closed, and its still open...and that was from a 2.2-CURRENT
machine as of March/96 ... how relevant can that be now, even if the
crashes continued? There has been *alot* of change over the past
year...the old PR should be closed, and a newer, more relevant one,
opened...IMHO...
IMHO, -CURRENT related PRs should die relatively quickly (6mos?),
-STABLE related slower (12mos?) and port-related *at least* when the port
gets upgraded...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980413005345.306D-100000>