Hopefully this helps clear up some questions The Outcome of the Vote `draft/` tag prefix is for drafts `rel/` tag prefix is for releases No more clean tags will be created [OPTIONAL] Existing clean tags should be removed as they were the OLD draft tags Responses
>> I would favor keeping both `x.x.x` and `rel/x.x.x` tags for the >> existing releases that were not rejected. The last item for removing the existing clean tags could be omitted from the request. I was only adding this as an additional proposal to perform the cleanup process that we lacked in the past. >> Am I right that with this proposal, we would not need to make >> `rel/x.x.x` tags for accepted releases after this proposal is >> accepted? No, we still be making `rel/` tags. `rel/` tags has and will always be the accepted release tag, unless changed in the future. We will no longer be making clean tags. Additional Information We never used clean tags as an official release. We have always told users that clean tags “are not official” and to “please wait for the rel/ tags and or NPM package” as those were considered our final and approved releases. If we want to switch from using the “rel/“ prefix to a clean tag (no prefix) for final releases, that should be a separate discussion and vote. The goal of this discussion/vote is focused only on: The draft tag prefixing (To remove confusion) The process of cleaning up of draft tags after release process (To keep our repo clean of clutter) Potentially the cleanup of existing drafts (To try and cleanup existing clutter) Side note about the clean tags: On one of my last releases, I created a draft clean tag to submit in a release vote email and within 10 minutes someone posted on Twitter that we have already released just based on the tag. This is why IMO clean tags should not be draft and probably not left around. > On Aug 19, 2020, at 8:30, Norman Breau <nor...@normanbreau.com> wrote: > > +1 on cleaning old draft tags > +1 on removing draft tags upon vote resolution (regardless of success or > failure) > > I don't have a strong preference for tag names, draft is fine to me, > especially as the default... If we run into a specific case during a release > discussion/vote where another tag name is preferable... we can be flexible > enough to discuss that in a release discussion thread for that particular > release. > Norman Breau > Software Developer > > nor...@normanbreau.com > (https://link.getmailspring.com/link/5668e2c6-02cf-4e96-96fa-160f5c615...@getmailspring.com/0?redirect=mailto%3Anorman%40normanbreau.com&recipient=ZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%3D%3D) > https://breautek.com > (https://link.getmailspring.com/link/5668e2c6-02cf-4e96-96fa-160f5c615...@getmailspring.com/2?redirect=https%3A%2F%2Fbreautek.com&recipient=ZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%3D%3D) > > On Aug 18 2020, at 9:40 am, Chris Brody <chris.br...@gmail.com> wrote: >>>> 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. >> >> -1 on "rc" on my part. I have seen other projects use "rc" to mean an >> rc version that comes before a stable version. >> >>> During the vote, people can append which tag name they prefer. >> +1 >>> Anyways, I don't want this decision and vote to end like last time because >>> of a tag name. >> +1 (+100) >>>> 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. >> >> I would favor keeping both `x.x.x` and `rel/x.x.x` tags for the >> existing releases that were not rejected. >> >>>> "rel/x.x.x" are used for the Apache archiving but I like the cleaner tags >>>> for users. >> +1. >> Am I right that with this proposal, we would not need to make >> `rel/x.x.x` tags for accepted releases after this proposal is >> accepted? >> >>> I am not looking to remove the `rel/` tag process. That must remain and >>> those tags will remain. >> +1 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> For additional commands, e-mail: dev-h...@cordova.apache.org >> >
