Bump version v2.0.0 (closed, renamed to v1.7.0)

[avas27JTG]

Summary

• GH-154: Created the settings command to change the preferences for meeting creation #284
• [GH-283]: Fixed issue #283 'Removed the code for depreciated JWT' #299
• [GH-152]: Updated instruction of adding scope to Oauth App #308
• [GH-300]: Fixed the JS error while posting meeting link to thread view #307
• [GH-240]:Fixed issue #240 edited the pretext of custom post #287
• [GH-309]: Removed mention of JWT setup from the README as it is no longer supported. #310
• Create new meeting causes an issue of generating multiple similar custom posts. #311
• /zoom settings [command] should be corrected. #312
• User not getting redirected to a new tab #313
• MM-54578 - Fixing zoom plugin button styles #305
• Moved images & updated legacy links #301
• Migrate Docs from GitBook #298
• fix rudder key secret name #295
• [MM-51751] Fix regex for tags trigger in CI/CD #294
• Implement webhook validation #279
• [MM-51269] Log errors from telemetry events #289
• Change codeowners to mickmister and trilopin #288
• Migrate from CircleCI to Github Actions #286
• Updated CodeQL to use latest version #281
• [GH-244] Update autocomplete help summary #251
• Check nil license features #277
• Revert "[GH-235] Refresh token on user level oauth (#235) (#242)" #268
• Create .gitpod.yml #258
• Make unhandled webhook events return 200 instead of 501 #257
• [GH-235] Refresh token on user level oauth (#235) #242
• fix typo on help-and-support.md #247
• Zoom installation docs update #245
• Create new meeting instead of using PMI #147
• /zoom start slash command posts in thread #228
• GH-200: Pass topic to zoom start #209
• dist: build linux/darwin arm64 targets #232

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ba2d98c) 19.33% compared to head (2d70109) 19.33%.
Report is 1 commits behind head on master.

❗ Current head 2d70109 differs from pull request most recent head 8b95f53. Consider uploading reports for the commit 8b95f53 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #321   +/-   ##
=======================================
  Coverage   19.33%   19.33%           
=======================================
  Files           9        9           
  Lines        1479     1479           
=======================================
  Hits          286      286           
  Misses       1138     1138           
  Partials       55       55           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mickmister]

Looking at the PR description, I don't think all of those PRs are new to this release. For instance, these two have definitely been released, and many more:

• Use ReactDOM webpack external #282
• For non-cloud plugin settings, set hosting property to on-prem #269

The process of determining what's in the new release is a bit of a manual process when we have the dot release cherry-picking process that we have. It doesn't need to be 100% accurate since this is difficult to verify, but try your best to pick out the work that is specific to this release. Essentially things that have built up on master that we didn't end up ever dot releasing, which I know is difficult because of the many different ways different people may have organized those commits when preparing the dot releases. What is usually built up in the master branch are non-urgent features and low impact defects.

Also, why is this specifically v2.0.0 and not a minor or dot release?

[AayushChaudhary0001]

Tested and Approved
Working fine in all the conditions, LGTM.

[mickmister]

To be more clear, here are the definitions to use to follow semantic version, or "semver":

https://semver.org

Given a version number Major.Minor.Patch, increment the:

Major - version when you make incompatible API changes
Minor - version when you add functionality in a backward compatible manner
Patch - version when you make backward compatible bug fixes

Additional labels for pre-release and build metadata are available as extensions to the Major.Minor.Patch format.

---

In our case this typically means:

• Major - Breaking changes and (significant) deprecations
• Minor - New features or significant change in how the program functions to the user. Basically a change in requirements of the program
• Patch/Dot - Bug fixes

In this case of this release, it will probably be a minor release, since I think there are new features here, and probably not any intentional breaking changes

[avas27JTG]

Yeah I agree with you @mickmister the only reason we were thinking of making it a major release was due to removal of the deprecated JWT settings from the plugin #299

Please let me know if we should create the release as 1.7.0 or 2.0.0 considering above change?

[avas27JTG]

@mickmister I've updated the description after removing the issues/PRs which were released in previous releases.

[mickmister]

the only reason we were thinking of making it a major release was due to removal of the deprecated JWT settings from the plugin #299

@avas27JTG That deprecation is really more of a deprecation from Zoom, and not so much our software. AFAIK the JWT offering doesn't work at all anymore on Zoom plugin version. Because of that, I don't think we should treat the new release as a breaking change in that regard. I think we should go with 1.7.0 for this release

[mickmister]

I removed some more from the list that are more clerical work, or have already been released. I think this may be more accurate:

• GH-154: Created the settings command to change the preferences for meeting creation #284
• [GH-283]: Fixed issue #283 'Removed the code for depreciated JWT' #299
• [GH-152]: Updated instruction of adding scope to Oauth App #308
• [GH-300]: Fixed the JS error while posting meeting link to thread view #307
• [GH-240]:Fixed issue #240 edited the pretext of custom post #287
• [GH-309]: Removed mention of JWT setup from the README as it is no longer supported. #310
• Create new meeting causes an issue of generating multiple similar custom posts. #311
• /zoom settings [command] should be corrected. #312
• User not getting redirected to a new tab #313
• MM-54578 - Fixing zoom plugin button styles #305
• [GH-244] Update autocomplete help summary #251
• Make unhandled webhook events return 200 instead of 501 #257
• Create new meeting instead of using PMI #147
• /zoom start slash command posts in thread #228
• GH-200: Pass topic to zoom start #209

[avas27JTG]

the only reason we were thinking of making it a major release was due to removal of the deprecated JWT settings from the plugin #299

@avas27JTG That deprecation is really more of a deprecation from Zoom, and not so much our software. AFAIK the JWT offering doesn't work at all anymore on Zoom plugin version. Because of that, I don't think we should treat the new release as a breaking change in that regard. I think we should go with 1.7.0 for this release

Sounds good, thanks for clarifying.

[mickmister]

FYI we always have to change this value too

Suggested change

	"release_notes_url": "https://github.com/mattermost/mattermost-plugin-zoom/releases/tag/v1.5.1",
	"release_notes_url": "https://github.com/mattermost/mattermost-plugin-zoom/releases/tag/v1.7.0",

[avas27JTG]

Noted, thanks

[avas27JTG]

@mickmister created a new PR #322 as I also changed the branch name to release-bump-1.7.0 in place of ...-2.0.0.