From: Dave Taht <d@taht.net>
To: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] Verifying/classifying/prioritizing bugs on a regular basis
Date: Sun, 17 Apr 2011 09:21:38 -0600 [thread overview]
Message-ID: <4DAB0582.1040903@taht.net> (raw)
1) I have a few people that get notified of new bug and feature requests
by default on the bismark issues page.
I can add more, let me know.
2) It would be good if various people could walk down the existing bug
and feature list and verify that a given bug exists, and comment on it
as to how to perhaps fix the problem.
And take ownership, provide an estimate as to how long it will take to
fix, add a start date, add watchers to people that might be interested, etc.
http://www.bufferbloat.net/projects/bismark/issues for everything
outstanding.
As a simple example, I'd like someone to replicate and verify that bug
88 exists...
3) Quite often this above task requires a joint, scheduled meeting, as
doing this sort of triage is not a lot of fun - but it is not required
to do it in person, over irc works well.
4) The default catagories of people on the list may not be correct. The
people with manager perms can promote/demote people into the right
catagories. For example, I'm closer to being a developer than a
contributor on this project...
reply other threads:[~2011-04-17 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DAB0582.1040903@taht.net \
--to=d@taht.net \
--cc=bismark-devel@lists.bufferbloat.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox