-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump version to 2.2.0. #709
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we get the open PRs that only require QA review into this release?
- [GH-418]: Fixed issue #418 'Added --exclude option to subscriptions command'. #683
- [GH-512,513] Fixed issue #512 and #513 on github plugin 'Updated subscription success messages' #661
- [GH-378]:Fixed issue #378 'Check for webhook while subscribing' #664
- [GH-693] Fix improper rendering of some unreads in the response of "/github todo" command #699
Sure, let me look |
@hanzei I added them to this release milestone, and the QA will start testing these issues, after which we can merge them into the master. |
…ub into release-bump-2.2.0
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #709 +/- ##
=======================================
Coverage 15.85% 15.85%
=======================================
Files 15 15
Lines 5778 5778
=======================================
Hits 916 916
Misses 4820 4820
Partials 42 42 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and approved
All the changes merged are working fine, LGTM.
@hanzei can you please approve the PR if it looks good to you? |
@mickmister |
@avas27JTG I'm genuinely not sure if bumping the min server version constitutes a new major version of the plugin. We haven't done that in the past. I'm thinking no, because the main reason we do major version changes is so that the admin is aware of breaking changes. In this case, the only side effect is they just won't be able to upgrade if they are on an older server version. There's not really a breaking change in that regard. |
Makes sense, thanks @mickmister we will keep it as a minor release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like (1/5) to get #712 into the release, but I'm fine with releasing the code as it is.
Yes, we have planned to include it here, this is in QA review currently. |
I think we should also try to get #718 into the release. Very small impactful PR |
@mickmister @hanzei #712 and #718 are now included. |
…hub into release-bump-2.2.0
@avas27JTG @AayushChaudhary0001 Are we good to merge the PR and cut the release? |
@hanzei I created an RC build and requested to be installed on community https://community.mattermost.com/core/pl/zd4h5ifbtjngbmi8d87we3x5wa |
Yes @hanzei we have created a playbook for it as per our release process and RC is also created by @mickmister |
…ub into release-bump-2.2.0
@avas27JTG @raghavaggarwal2308 Are there any recent changes to the master branch that we don't want to include in this release? Wondering if we can get this in there #729. Let me know, and I'll cut another RC with the latest changes |
@mickmister No I think we can cut the RC with latest changes. We have just merged the changes for description issue and |
@raghavaggarwal2308 Can you please merge the latest into this branch to get #729 into the release? |
…ub into release-bump-2.2.0
@mickmister The branch and PR description is updated now |
@mickmister Are we good to cut the release? Is there anything blocking it? |
Summary