Arvados

2.1.1~rc1

arvados 5efbca2174eefd17f7b249a0662aeb30de4ec9c5

2.1.1~rc2-1

arvados|a7ede72ed820371d39385bbae5c9be42889cf8fa

2.1.1~rc3-1

arvados|4f9de1f006ce329f76eb3c73a1b819b2ad60f67f

2.1.1~rc4-1

arvados|bdc3e037a13d31848886d1f114f72fd6659cdd83

build-and-publish-rc-packages: #74

arvados-workbench2|e29832f3cd252b819a998c5c7c09e7de6735365e

2.1-workbench2-build-release-candidate-package: #1

Draft release notes https://www-dev.arvados.org/release-notes/2.1.1/

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?

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!

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.

2.1.1-1

arvados|bdc3e037a13d31848886d1f114f72fd6659cdd83

build-and-publish-rc-packages: #76

arvados-workbench2|e29832f3cd252b819a998c5c7c09e7de6735365e

2.1-workbench2-build-release-candidate-package: #2