Skip to content
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

Merged
merged 6 commits into from
Feb 13, 2024
Merged

Conversation

avas27JTG
Copy link
Contributor

@avas27JTG avas27JTG commented Nov 9, 2023

Summary

Copy link
Contributor

@hanzei hanzei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hanzei hanzei added 2: Dev Review Requires review by a core committer 3: QA Review Requires review by a QA tester labels Nov 9, 2023
@hanzei hanzei added this to the v2.2.0 milestone Nov 9, 2023
@avas27JTG
Copy link
Contributor Author

Can we get the open PRs that only require QA review into this release?

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.

@codecov-commenter
Copy link

codecov-commenter commented Nov 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7da125a) 15.85% compared to head (ff05dfc) 15.85%.

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.
📢 Have feedback on the report? Share it here.

Copy link

@AayushChaudhary0001 AayushChaudhary0001 left a 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.

@avas27JTG
Copy link
Contributor Author

avas27JTG commented Nov 28, 2023

Can we get the open PRs that only require QA review into this release?

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?

@avas27JTG
Copy link
Contributor Author

@mickmister min_server_version is changed to 7.1.0 in this PR #598 so, should we still keep this release as v2.2.0 or change it to v3.0.0?.

@mickmister
Copy link
Member

@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
Copy link
Contributor Author

@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.

Copy link
Contributor

@hanzei hanzei left a 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.

@hanzei hanzei removed the 2: Dev Review Requires review by a core committer label Nov 30, 2023
@avas27JTG
Copy link
Contributor Author

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.

@mickmister
Copy link
Member

I think we should also try to get #718 into the release. Very small impactful PR

@avas27JTG
Copy link
Contributor Author

@mickmister @hanzei #712 and #718 are now included.

@hanzei
Copy link
Contributor

hanzei commented Dec 5, 2023

@avas27JTG @AayushChaudhary0001 Are we good to merge the PR and cut the release?

@mickmister
Copy link
Member

@hanzei I created an RC build and requested to be installed on community https://community.mattermost.com/core/pl/zd4h5ifbtjngbmi8d87we3x5wa

@avas27JTG
Copy link
Contributor Author

@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

@mickmister
Copy link
Member

@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

@raghavaggarwal2308
Copy link
Contributor

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 (#735).

@mickmister
Copy link
Member

mickmister commented Feb 9, 2024

@raghavaggarwal2308 Can you please merge the latest into this branch to get #729 into the release?

@raghavaggarwal2308
Copy link
Contributor

@mickmister The branch and PR description is updated now
cc: @avas27JTG

@hanzei
Copy link
Contributor

hanzei commented Feb 13, 2024

@mickmister Are we good to cut the release? Is there anything blocking it?

@mickmister
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3: QA Review Requires review by a QA tester
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants