You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Table of Contents
|
First Pass: General Review
Who: Chris and Volunteers
When: Late March
For all Unresolved Issues:
- If it's no longer relevant, close as WontFix
- If it's a duplicate, link to duplicate-of and close as Duplicate
- If it's in the "Recieved" state, determine if it can be opened or should stay closed. If neither, note why in the comments.
- Review metadata for completeness + accuracy (don't worry about the fix version, but do take a guess at relative priority)
Second Pass: Scoping for 3.4
Who: Steve and Chris
When: Late March-Early April
Note: At this point, it doesn't matter if we think the issues can be resolved in time for the release. We're just saying they're "fair game" for 3.4.
For all Open Bugs:
- Mark it for 3.4 if it doesn't involve major architectural changes
For all Open Features or Improvements:
- Mark it for 3.4 if it doesn't involve major architectural changes and ANY of the following apply:
- it's something we've already talked about it for 3.4
- it's well-defined and easy to do
- we already know of someone who is planning to work on it for 3.4
Third Pass: Assignments for 3.4
Who: Steve and Committers
When: Early-Mid April
For all Open Issues scoped for 3.4:
- If an assignee is defined, verify they'll be able to work on it
- If a committer is willing to work on it, add them as the assignee
- If we have no assignee yet, add to "Call for Participation" under Miscellaneous
|
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))