Date: Fri, 23 Feb 2007 19:57:50 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Remko Lodder <remko@elvandar.org> Cc: bugbusters@FreeBSD.org Subject: Re: status? Message-ID: <20070223195750.5e82a475.trhodes@FreeBSD.org> In-Reply-To: <45DF47A1.3020305@elvandar.org> References: <45DF47A1.3020305@elvandar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 Feb 2007 20:59:29 +0100 Remko Lodder <remko@elvandar.org> wrote: > Hello Bugbusters of the FreeBSD team, > > Currently I am looking into older kern/i386/bin PR tickets > that are having patches or are in feedback mode. I am trying > to resolve them and get rid of them in general. > > I can use a little help though, there are specific PR's > mentioning specific versions of FreeBSD (4.x for example), > which might no longer apply to more recent FreeBSD versions > (6.x preferrably). Wow. I've kicked this back and forth since I did the handbook changes. It was then I began thinking of how to deal with this. Admittedly so, I'll probably pull my hair out and scream if I need to look over each and every document in our tree and garbage collect 4.X stuff - updating and finishing parts as I can. In the case of PRs (both code and doc), the process is much more in depth. While I'd like to say "just close them and wait for another PR for 5/6/7" that is just bad handling. So my opinion is just coming up with some kind of .plan for dealing with them. It could as simple as play the normal reply asking about it, try to reproduce yourself, etc. Or you could go back and start by seeing if the files even exist, if the issue with a merged subsystem or a deprecated subsystem or code, and so on. Guess what I mean is, damn, that's a huge project. :( -- Tom Rhodes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070223195750.5e82a475.trhodes>