You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Table of Contents

Work in progress

Currently being edited, please come back later!

This page lists

  • Current development status of JIRA issues in Milestone 4
  • Current testing status of JIRA issues in release 3.4
  • Current documentation update status for JIRA issues in release 3.4

Fedora 3.4 Milestone 3 Development Status

All issues currently assigned to Milestone 4, 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.

was:

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 Plan

Issues 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-492 Allow DC, RELS-EXT, etc, to be Managed Content (Unassigned)
FCREPO-648 Move to a modern DI framework (Unassigned)
FCREPO-683 Enhanced Content Models (Unassigned)
FCREPO-509 REST API does not properly handle ingests with FOXML that does not contain a PID (Unassigned)
FCREPO-627 Fedora REST-style object viewer does not properly handle encoded slashes in the pid value. (Unassigned)
FCREPO-654 Add REST API methods for exposing and manipulating relationships (Unassigned)
FCREPO-675 Implement getDatastreamHistory on REST API (Steve)
FCREPO-679 Issues in Fedora Commons installation (Unassigned)
FCREPO-680 REST API throws NPE when adding new datastream without providing media- and mime type (Unassigned)
FCREPO-687 Create "Upload" method in REST API (Unassigned)

FCREPO-696 Adding datastream with managed content throws Exception when providing a checksum (Unassigned)
FCREPO-700 REST api export specifies the wrong media type for atomZIp archives (Unassigned)
FCREPO-453 Allow the retrieval of content via the file URI scheme (Unassigned)
FCREPO-568 json/jsonp output format for risearch (Unassigned)
FCREPO-608 Put /objects/{pid} (modifyObject) has state default to A, so will always set objects active, unless told not to (Unassigned)
FCREPO-609 Purge object will throw general exception if force=true (Unassigned)
FCREPO-613 Purge datastream will throw a general exception if force=true (Unassigned)
FCREPO-615 With FeSL enabled, authentication is required for every resource (Unassigned)
FCREPO-638 Fedora basic search interface returns results with old-style "/fedora/get" URLs instead of new REST interface URLs (Unassigned)
FCREPO-64 Datastream SIZE attribute not fully implemented (Unassigned)
FCREPO-671 Allow use of FeSL AuthN without FeSL AuthZ during install (Unassigned)
FCREPO-699 PUT /objects/{pid}/datastreams/{dsid} sets versionable to true if it is not specified (REST API) (Unassigned)
FCREPO-703 REST API calls to getDatastreamDissemination fails when XACML enabled, API-A auth disabled (Unassigned)
FCREPO-704 Ingesting a managed content datastream via REST fails with files larger than 2GB (Unassigned)
FCREPO-708 REST API purgeDatastream returns HTTP 204 No Content instead of the dates of the deleted versions (Unassigned)
FCREPO-712 Date strings with milliseconds are parsed incorrectly (Unassigned)

Fedora 3.4 System Tests

NB: Test failures with FeSL AuthN enabled (the default), the following are with FeSL AuthN disabled

Not tested:

  • OSX
  • stand-alone Tomcat
  • other application servers
  • MPTStore
  • Rebuilder
  • Swing admin client
  • Web admin client
  • RMI receiver tests
  • GSearch sanity test
  • OAIProvider sanity test
  • Oracle
  • MS SQL Server

Fedora 3.4 Documentation Plan

Issues 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)
FCREPO-648 - Move to a modern DI framework (Unassigned)
FCREPO-654 - Add REST API methods for exposing and manipulating relationships (Unassigned)
FCREPO-675 - Implement getDatastreamHistory on REST API (Steve)
FCREPO-683 - Enhanced Content Models (Unassigned)
FCREPO-687 - Create "Upload" method in REST API (Unassigned)
FCREPO-689 - Enable optimistic locking for modify operations (Unassigned)
FCREPO-453 Allow the retrieval of content via the file URI scheme (Unassigned)
FCREPO-609 Purge object will throw general exception if force=true (Unassigned)
FCREPO-613 Purge datastream will throw a general exception if force=true (Unassigned)
FCREPO-621 Move to Java6+ (Java 5 no longer supported) (Unassigned)
FCREPO-627 Fedora REST-style object viewer does not properly handle encoded slashes in the pid value. (Unassigned)
FCREPO-630 Switch to SLF4J with Logback as primary logging framework (Unassigned)
FCREPO-64 Datastream SIZE attribute not fully implemented (Unassigned)
FCREPO-671 Allow use of FeSL AuthN without FeSL AuthZ during install (Unassigned)
FCREPO-708 REST API purgeDatastream returns HTTP 204 No Content instead of the dates of the deleted versions (Unassigned)

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels