#### Remaining PRs - [x] #745 -- ready for @pitbulk review. Blocked due to JRuby failure due to Nokogiri bug, maybe we should just merge it anyway. - [x] #758 - [x] #759 - [ ] @johnnyshields to confirm v2.x branch works with known attack vectors - [ ] @johnnyshields to change all deprecation removal notices to v3.0.0 (instead of v2.1.0, to be Semver compliant) and add UPGRADING notice. - [ ] @johnnyshields to raise PR to refactor error handling #### Release Steps - [x] Release current master as 1.7.0 gem (can be done now) - [ ] Move `master` branch to `1.x-stable` branch (can be done now) - [ ] Push `v2.x` branch to `master` and release 2.0.0 gem. - [ ] Create `v2.0.x-stable` branch. (`master` will be for `2.1.x` development, `v2.0.x-stable` is for 2.0.1, 2.0.2, etc. backports.) #### Post-release plans for 2.1 / 3.0 - [ ] https://github.com/SAML-Toolkits/ruby-saml/issues/693 - [ ] https://github.com/SAML-Toolkits/ruby-saml/issues/775 - [ ] Further Rubocop cleanup -- get to 100% clean - [ ] Migrate tests to RSpec?
Remaining PRs
Release Steps
masterbranch to1.x-stablebranch (can be done now)v2.xbranch tomasterand release 2.0.0 gem.v2.0.x-stablebranch. (masterwill be for2.1.xdevelopment,v2.0.x-stableis for 2.0.1, 2.0.2, etc. backports.)Post-release plans for 2.1 / 3.0