Release Notes
Issues discovered in testing
Issues discovered in testing:
Issue | bb | db | nw | |
---|---|---|---|---|
1 | Re the orphaned chunk issue ( ), it appears that orphanned chunks are not removed when the file that is being updated is identical to the one in duracloud. There is one way around it: jumpstart mode. When the synctool is in jumpstart mode, the file is retransferred and the chunks are removed.So the scenario we are talking about is as follows:
We have a tool for identifying orphanned chunks and removing them which we have used successfully in the recent past. We could force the synctool to perform a cleanup when it detects matching files. Or we could support that feature when a flag is enabled. Or it would also be possible to prevent the cleanup, when a flag is present. As far as duracloud operations are concerned, making cleanup on matching files the default behavior and providing a flag to suppress it for power users is optimal since we won't have to worry about scrubbing spaces after users upgrade to 6.1.0. For the users, the best option is for us not to implement "cleanup on checksum match" behavior at all and scrub their repositories once they upgrade to the new synctool. |
Testing of Completed Issues
Item | bb | db | nw |
---|---|---|---|
N/A | |||
N/A |
Regression Testing
Task | bb | db | nw |
---|---|---|---|
Perform Regression Tests | |||
Use ZAProxy to perform a security analysis
|
Build Tests
Test | bb | db | nw |
---|---|---|---|
mvn clean install (full build + integration tests) - DuraCloud |
Release Actions - for each baseline (in this order): DB, DuraCloud, MC, Snapshot, Mill
- Complete testing
- Perform version release (v6.1.0): https://github.com/duracloud/deployment-docs/blob/master/release-new-version.md
- Deploy release zip to production Beanstalk
- Update documentation
- Create release notes in Github