This page lists
Fedora 3.4 Milestone 3 IssuesWork-in-progress issues from Milestone 2 have been carried over to Milestone 3. In addition to these, based on the prioritisation from Milestone 2 and the priority of recently-submitted issues, the following is a candidate list of issues in priority order (highest priority first) for Milestone 3. It is not anticipated that there'll be sufficient time and resources available to complete all of these issues. Please assign yourself to issues you feel you're able to take on and complete by the 3.4 release code freeze on Friday June 25. Where possible please assign yourself and work on issues in priority order.
If you feel you're best able to contribute by working on issues outside of this list, that's would also be welcomed. It would be useful if you could take account of the priority of the issues when selecting issue that you are available to contribute to. If you assign yourself to any issues outside of the candidate list for Milestone 3 then please let Steve know by email. Fedora 3.4 Milestone 3 Development StatusAll issues currently assigned to Milestone 3, and their current development status from JIRA. jiraissues: com.atlassian.confluence.extra.jira.exception.JiraIssueMacroException: com.atlassian.confluence.macro.MacroExecutionException: Data cannot be retrieved due to an unexpected error.
Fedora 3.4 Test PlanIssues in Release 3.4 that require testing. Please assign yourself (by putting your name in brackets) to any issues that are not assigned to a tester, and indicate the result of your testing by clicking Pass or Fail. Unknown macro: {testplan}
FCREPO-689 Enable optimistic locking for modify operations (Unassigned) FCREPO-696 Adding datastream with managed content throws Exception when providing a checksum (Unassigned) Fedora 3.4 Documentation PlanIssues in Fedora 3.4 that require documentation updates. Please assign yourself (by putting your name in brackets) to any issues that are not assigned, when you have either updated the documentation or verified that it is up-to-date, please indicate this by clicking Pass. Please ensure that any documentation changes include a warning indicating that the changes apply to Fedora 3.4 which has not been release yet, eg: Fedora 3.4 This documentation applies to Fedora 3.4, which has not yet been released. Unknown macro: {testplan}
FCREPO-492 - Allow DC, RELS-EXT, etc, to be Managed Content (Unassigned) |