> > 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
