> At this point I think almost all clean tags should match accepted rel > (release) tags. > > Any clean tags that are for rejected drafts should definitely be deleted. > > Just as a small, personal preference, I would not favor deleting any > clean tags that already match accepted rel (release) tags.
+1 Understood. For this vote, existing clean tags will not be removed as part of a cleanup process. If I come across any tags that does not have a `rel/` tag, I will make a note and potentially open a separate vote for those specifically. > On Aug 19, 2020, at 10:48, Chris Brody <chris.br...@gmail.com> wrote: > >> `draft/` tag prefix is for drafts > > +1 > >> `rel/` tag prefix is for releases > > +1 > >> No more clean tags will be created > > OK as discussed below > >> `rel/` tags has and will always be the accepted release tag, unless changed >> in the future. > > +1 > >> 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. > > yup > >> 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. > > +1 > >> 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. > > At this point I think almost all clean tags should match accepted rel > (release) tags. > > Any clean tags that are for rejected drafts should definitely be deleted. > > Just as a small, personal preference, I would not favor deleting any > clean tags that already match accepted rel (release) tags. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org >
