In order to properly scope pre-existing items for the 3.4 release, and ensure the quality/relevance of the items in the tracker, a multi-pass review of of the relevant issues in JIRA is planned.

First Pass: General Review

Who: Chris, Steve and Volunteers
When: Early April

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)

Issues Reviewed:

• FCREPO-9 through FCREPO-190

Issues Needing Discussion:

• Enter here

Second Pass: Scoping for 3.4

Who: Steve and Chris
When: Early-Mid 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: 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