...
As such, the process for moving to the production release of Fedora 6.0 will include both Alpha and Beta releases to ensure the broader community has ample opportunity to confirm the functionality against local needs and use cases, and to provide feedback from local testing.
Alpha
One of the goals with the Fedora 6.0 release is to retain compliance with the featureset found in Fedora 5.1 which includes continuing to be compliant with the Fedora API Specification.
The Alpha release includes the following features:
...
Additionally, the following features will be in the Beta release of Fedora 6.0.0 but are not found in the Alpha:
- Support for LDP Indirect Containers
- Targeted rebuild of side-loaded OCFL objects
- Search service user interface
- Migration of Fedora 4 ACLs to Fedora 6
- Support for LDP Indirect Containers
- Support for the http://www.w3.org/ns/oa#PreferContainedDescriptions header
- No more http://fedora.info/definitions/v4/repository#RepositoryRoot RDF type on repository root
- Migration of Fedora 4 ACLs to Fedora 6
- Migration of Fedora 5 repositories rooted at '/fcrepo' to Fedora 6
...
Breaking changes from Fedora 5.x
The following are breaking changes in Fedora 6 that should be considered if porting a client application that interacted with a Fedora 5 repository:
- API for creating and managing Transactions has changed
- POST-ing to a URL which does not exist will now create the destination as a pseudo-container, i.e. "ghost node", and create a child node inside of it. Previously, this would result in a 404
- Memento timestamps may no longer be specified when creating a memento
- Mementos cannot be deleted
- ActivityStream Actors, in event notifications, now correctly contain a single type rather than a list of typesAPI for creating and managing Transactions has changed
- No more http://fedora.info/definitions/v4/repository#hasParent property on nested containers
- No more http://fedora.info/definitions/v4/repository#writable property on resources
Fedora API Compliance
The One of the goals of the Fedora 6.0 release is to retain compliance with the featureset found in Fedora 5.1 which includes continuing to be compliant with the Fedora API Specification.
The Alpha release of Fedora 6 .0-alpha build has the following results when the Fedora API TestSuite is run against it. Before the production release of Fedora 6, we strive to have 100% compliance with this test suite.
| Req Level | Num Pass | Num Fail | Num Skip | % Pass |
|---|---|---|---|---|
| MUST | 142 | 7 | 6 | 95% |
| SHOULD | 38 | 5 | 1 | 88% |
| MAY | 23 | 1 | 18 | 96% |
| Total | 203 | 13 | 25 | 94% |
...
| Expand | ||
|---|---|---|
| ||
|
For comparison, here is are the results of Fedora 5.1.1 are:
| Req Level | Num Pass | Num Fail | Num Skip | % Pass |
|---|---|---|---|---|
| MUST | 146 | 3 | 6 | 98% |
| SHOULD | 43 | 0 | 1 | 100% |
| MAY | 30 | 0 | 12 | 100% |
| Total | 219 | 3 | 19 | 99% |
Full results can be found at https://fedora.info/spec-tests/.
Upgrading to the Alpha
In conjunction with the Fedora 6.0 Alpha release comes upgrade tooling that allows for migrating Fedora 3, 4 and 5 repositories to Fedora 6.0. Please see the Migrate to Fedora 6 instructions for details on how to perform these upgrades.
Beta
Community integrations
...
The Islandora community will build a new fcrepo container using ISLE and encourage our community to pull it in and test using Fedora 6. We will manually test integration by walking through our Fedora relevant use cases. We will seek to test:
- Green-field installations
- Existing Islandora 8 installations
- Islandora 7 installations that are migrating into Islandora 8
...
- How many resources can be ingested into Fedora? How long does it take?
- How do POST response times change on binary resources as the size of the binaries increases?
- How do GET/POST response times change as the size of the repository increases?
- How do GET/POST response times change as on a compound resource as the number of resource versions increases?
- How do GET response times change on binary resources as the number of binary resources in the repository increases?
- How do GET response times change on containers as the number of child and/or member resources increases?
- etc
Feedback
Community testing and feedback is vital during the the Alpha and Beta phases of Fedora 6.0 in order to ensure that the application meets (exceeds?) the needs of production use cases. Any feedback that you have during the testing process will be valuable to know; good or bad.
Please use any of the project communication channels for sharing your results: Mailing Lists etc.