> The name "draft" for tags in the release process is not that clear to me. I > suggest "rc" for release candidate. And yes we should clean these tags up.
The naming is not what is important, it is the idea. Since last time I think this topic died because people couldn’t decide on a naming convention, I am setting a hard rule for this vote so it can process accordingly with no blocks. During the vote, people can append which tag name they prefer. The tag with most points will be used, the default fallback will be `draft/`, and if no tag is provided during the vote, default will be used. For example vote scenario: Vote Scenario 1: +1 rc +1 draft +1 temp `draft/` will be used. Vote Scenario 2: +1 rc +1 draft +1 rc `rc/` will be used. Vote Scenario 3: +1 +1 draft +1 rc `draft/` will be used. Anyways, I don't want this decision and vote to end like last time because of a tag name. > I am not sure about removing all tags without the rel prefix and not creating > these anymore. These are easy to remember and type tags to get a specific > version. Personally I would keep them and create them with the new process > after a vote too. "rel/x.x.x" are used for the Apache archiving but I like > the cleaner tags for users. I am trying to clean up the repos as well. Keep draft tags are not idea IMO. Some repos have 141 tags and half of those are most likely the draft tags which has a corresponding rel tag with identical commit ids. > "rel/x.x.x" are used for the Apache archiving but I like the cleaner tags for > users. I am not looking to remove the `rel/` tag process. That must remain and those tags will remain. > On Aug 18, 2020, at 15:48, Niklas Merz <niklasm...@apache.org> wrote: > > I agree that our current process creates confusion in the community. > > The name "draft" for tags in the release process is not that clear to me. I > suggest "rc" for release candidate. And yes we should clean these tags up. > > I am not sure about removing all tags without the rel prefix and not creating > these anymore. These are easy to remember and type tags to get a specific > version. Personally I would keep them and create them with the new process > after a vote too. "rel/x.x.x" are used for the Apache archiving but I like > the cleaner tags for users. > > > August 18, 2020 8:39 AM, "Bryan Ellis" <er...@apache.org> wrote: > >> 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. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org >
