Closed avas27JTG closed 6 months ago
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
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.
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
7da125a
) 15.85% compared to head (ff05dfc
) 15.85%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
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.
@hanzei can you please approve the PR if it looks good to you?
@mickmister min_server_version
is changed to 7.1.0
in this PR https://github.com/mattermost/mattermost-plugin-github/pull/598 so, should we still keep this release as v2.2.0
or change it to v3.0.0
?.
@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.
@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.
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 https://github.com/mattermost/mattermost-plugin-github/pull/718 into the release. Very small impactful PR
@mickmister @hanzei #712 and #718 are now included.
@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
@avas27JTG @AayushChaudhary0001 Are we good to merge the PR and cut the release?
Yes @hanzei we have created a playbook for it as per our release process and RC is also created by @mickmister
@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 https://github.com/mattermost/mattermost-plugin-github/pull/729. Let me know, and I'll cut another RC with the latest changes
Are there any recent changes to the master branch that we don't want to include in this release?
@mickmister No I think we can cut the RC with latest changes. We have just merged the changes for description issue and see more
link in the tooltip after our last RC (https://github.com/mattermost/mattermost-plugin-github/pull/735).
@raghavaggarwal2308 Can you please merge the latest into this branch to get https://github.com/mattermost/mattermost-plugin-github/pull/729 into the release?
@mickmister The branch and PR description is updated now cc: @avas27JTG
@mickmister Are we good to cut the release? Is there anything blocking it?
@hanzei Yes I think we're good to go. We've had 36e72f4 running on community for a bit now, and only a few changes/fixes have been added since then.
Summary