Project

General

Profile

Actions

Support #17043

closed

Arvados 2.1.1

Added by Peter Amstutz over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Due date:
Story points:
-
Release relationship:
Auto

Subtasks 17 (0 open17 closed)

Task #17120: 17. Release announcementResolvedPeter Amstutz11/18/2020Actions
Task #17121: 16. Update arvados.orgResolvedPeter Amstutz11/18/2020Actions
Task #17122: 15. Tag git commitsResolvedPeter Amstutz11/18/2020Actions
Task #17123: 14. Publish docker image, python & ruby packagesResolvedPeter Amstutz11/18/2020Actions
Task #17124: 13. Publish packages to stableResolvedPeter Amstutz11/17/2020Actions
Task #17125: 12. Sign off on releaseResolvedPeter Amstutz11/17/2020Actions
Task #17126: 11. Test playground / su92lResolvedPeter Amstutz11/17/2020Actions
Task #17127: 10. Deploy RC to su92lClosedJavier Bértoli11/17/2020Actions
Task #17128: 9. Run WGS pipeline on playgroundResolvedPeter Amstutz11/17/2020Actions
Task #17129: 8. Deploy RC on playgroundResolvedPeter Amstutz11/17/2020Actions
Task #17130: 7. Review release notesResolvedLucas Di Pentima11/16/2020Actions
Task #17131: 6. Write release notesResolvedPeter Amstutz11/16/2020Actions
Task #17132: 5. Build RC packagesResolvedPeter Amstutz11/16/2020Actions
Task #17133: 4. Record git commitsResolvedPeter Amstutz11/16/2020Actions
Task #17134: 3. Create next point release in RedmineResolvedPeter Amstutz11/16/2020Actions
Task #17135: 2. Review releaseResolvedLucas Di Pentima11/16/2020Actions
Task #17136: 1. Prep RC branchResolvedPeter Amstutz11/16/2020Actions
Actions #2

Updated by Peter Amstutz over 3 years ago

  • Target version changed from 2020-11-04 Sprint to 2020-11-18
Actions #3

Updated by Peter Amstutz over 3 years ago

  • Release set to 36
Actions #5

Updated by Peter Amstutz over 3 years ago

  • Tracker changed from Bug to Support
Actions #9

Updated by Lucas Di Pentima over 3 years ago

Commits look good. The only detail is that some branches seem to have been merged commit by commit instead of cherry picking the merge commit to master.

Also #16812 (wb2 story) wasn't finished yet so it maybe it should be moved to another release?

Actions #10

Updated by Lucas Di Pentima over 3 years ago

Release notes comments:

  • The comment about #16005 & #16812 could include an explanation about the uses of the “copy to clipboard” feature (ie: bookmarking, sharing, ...)
  • It seems to me that #17040 is explained in too much detail. How about something along the lines: “Improved performance on permissions checking, by adding caching and fixing database misbehavior"

The rest looks good to me!

Actions #11

Updated by Peter Amstutz over 3 years ago

Lucas Di Pentima wrote:

Commits look good. The only detail is that some branches seem to have been merged commit by commit instead of cherry picking the merge commit to master.

You can't cherry-pick merge commits, and you can't merge the original branch without bringing every change in master into the release branch.

To get a merge commit, I would have to effectively cherry-pick the original branch into a 2.1-dev branch and then merge it with 2.1-dev. It is fewer steps to cherry-pick the branch commits directly, and the result is the same.

Also #16812 (wb2 story) wasn't finished yet so it maybe it should be moved to another release?

Yes, that's makes sense.

Actions #12

Updated by Peter Amstutz over 3 years ago

  • Status changed from New to In Progress
Actions #14

Updated by Peter Amstutz over 3 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF