This discussion is to update our release process, potentially improve community
understanding, and as well cleaning up after a successful or failed release.
I want the following rules to be implemented and will start the vote after
keeping this discussion open within 24 hours for any modifications,
suggestions, feedback, or additions.
1. Prefix our draft tags with `draft/`
Currently, all of our draft tags, used for release, do not contain any
prefix and shows only a version number.
It appears this creates confusion within the community. Too many people
always ask, "Why is the version not released in npm". I have always noticed
these questions only when the draft tag exists.
I am hoping that this addition to the release process will help reduce some
of the confusion.
2. After a successful or failed vote, remove the `draft/` tag
IMO, keeping the draft tag is not necessary. It is supposed to be a
temporary tag used only during the voting process.
To reduce the clutter in our GH repos, it would be nice to remove these
draft tags.
If anyone is relying upon a draft tag in a production environment, the
usage was their own risk.
Also, with the addition of the two rules above, I will append to the vote as
well the cleanup request to remove all current existing draft tags from all of
our repos. Only tags that have a `rel` tag will be removed.
For example, if there is a tag `1.0.0` and `rel/1.0.0`, then tag `1.0.0` will
be removed.
If there is a tag that doesn’t have a `rel` tag, it will not be deleted and a
future email will be created to discuss these unknown tags to figure out what
action to be performed.
We had this discussion before but never started a vote thread. I will be
creating that thread shortly.
