Re: The way to the next dpkg release
Frank Lichtenheld <djpig@debian.org> writes:
> I propose the following timeline for the next release:
> Commit patches until Sunday January, 22th (5 days from now).
> This should give plenty of time to at least work through
> the backlog some of us have aquired (My own one can be seen
> at http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=djpig@debian.org;tag=fixed-in-my-arch-branch).
> Give a few days of testing at the beginning of next week.
> Upload around Thursday January, 26th.
> Comments, objections?
I'm not entirely sure that I'm going to have time, so I'm a little
hesitant to be volunteering, but since the details may help someone else
even if I turn out not to have the time....
One of the difficulties that I see with dpkg at the moment is that it has
a very large bug list. Many of those bugs are very old, the use of tags
is sometimes different from bug to bug, and the database could probably
use either a good set of usertags or some bug title massaging (or possibly
both).
I've been looking a little for a package to do bug triage on when I have
the time, and this always looked like an excellent target if I had some
guidelines as to what the maintainers wanted. Now seems like a great
opportunity to come up with some guidelines so that some of the rest of us
can pitch in and start getting the bug list down to something more
reasonable.
So, any general thoughts on a bug policy? Use of confirmed / patch / etc?
Categories of bugs that we should create with usertags?
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: