Mattermost-server: Support --pre-release in matterbuild's cutplugin command

[mattermod]

We often use matterbuild's cutplugin command to cut plugin releases, i.e.:

/mb cutplugin --repo mattermost-plugin-incident-response --tag v0.7.0-alpha.1

However, by default, this results in that version being labelled as the most recent release instead of a pre-release. Let's extend cutplugin with a --pre-release flag to change this behaviour:

/mb cutplugin --repo mattermost-plugin-incident-response --tag v0.7.0-alpha.1 --pre-release

---

If you're interested please comment here and come join our "Contributors" community channel on our daily build server, where you can discuss questions with community members and the Mattermost core team. For technical advice or questions, please join our "Developers" community channel.

New contributors please see our Developer's Guide.

JIRA: https://mattermost.atlassian.net/browse/MM-29289

[avinashdhinwa]

I would like to work on this

[avinashdhinwa]

@lieut-data Wanted to understand that would we want to say explicitly --pre-release or --release, I don't have any context here I mean what would release do but I believe having --pre-release by default will never hurt. What are you thoughts on this?

[avinashdhinwa]

@lieut-data Wanted to understand that would we want to say explicitly --pre-release or --release, I don't have any context here I mean what would release do but I believe having --pre-release by default will never hurt. What are you thoughts on this?

Ofcourse this depends on if:

• we publish more of pre-releases or releases
• we want to have the same params as github api

[lieut-data]

Good question, @avinashdhinwa! My original thought was to make --pre-release optional, so that the default behaviour is preserved. But your arguments resonate with me -- @hanzei, I'm curious on your thoughts here. Would it be valuable to assume --pre-release by default, and force a --release to do otherwise?

[hanzei]

Good question, @avinashdhinwa! My original thought was to make --pre-release optional, so that the default behaviour is preserved. But your arguments resonate with me -- @hanzei, I'm curious on your thoughts here. Would it be valuable to assume --pre-release by default, and force a --release to do otherwise?

I like the proposal in https://github.com/mattermost/matterbuild/pull/52 to have a --pre-release and don't tag as pre-release by default. Most of the the releases are "normal" ones.