[OPEN-ILS-DEV] Bug Targeting Practices?

[Ben Shum]

These questions are aimed mostly for Jason, our head bug wrangler, but I
would appreciate any other suggestions for best practices when helping
with bug management on Launchpad.

How do we decide which bugs we target to different milestones?  Is that
action designed to put a face on bugs that require fixing prior to the
release we target?  Or that the bug is planned and assigned to be fixed
by that target milestone?

I can see we have quite a few bugs queued with no milestone action and
that do not seem have been adjusted recently.  If still confirmed as
unfixed and not marked as wishlist items, should we aim to target them
to a new milestone if they have not been fixed yet?  Or just leave as is
and only direct our attention to apply targets for new bugs first?

Also, what do we do in situations where a bug has been confirmed to
apply for both 1.6.1.x and 2.0?  Should we target for the most recent
milestone (i.e. 2.0?) or nominate the bug to apply to multiple branches
and await release team confirmation?

Let me know what we should be doing or if I should bring these questions
up at a dev meeting / bug wrangling day in the future.

-- Ben

-- 
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113