I'm not willing to do anything on any hill here either and I'd rather
gel with the team consensus, I've said my bits ;-)
Gary
On Tue, May 2, 2023 at 4:10 PM Volkan Yazıcı wrote:
>
> Email archives are irrelevant for the provenance of sources; an arbitrary
> tag/commit not sealed with `rel/`
Email archives are irrelevant for the provenance of sources; an arbitrary
tag/commit not sealed with `rel/` prefix might disappear and we will lose
the context to "what was proposed/rejected for release" .
We don't have hundreds of releases with dozens of RCs for each. I would
rather see my `git
What you are proposing IMO is confusing and clutters up the release tag
space: "rel" stands for "releases", not for "candidates for releases that
may be completely broken" :-(
It is of zero use to downstream users, and it is only being proposed out of
the convenience because some tool does it,
I support the idea of using `rel/`-prefixed tags both for releases and RCs
(release candidates). It matters for provenance, which is of subject for
RCs too, in particular, the downvoted ones. Next to that, it is intuitive,
one doesn't need to remember two different patterns to access releases and
Hi Ralph,
On Tue, 2 May 2023 at 06:31, Ralph Goers wrote:
>
> One more issue. I see no reference to a web site containing release notes and
> a download page. At a minimum the download page is required to send the
> announcement email.
Sorry, I forgot to give the link in the vote e-mail. The
Hi Ralph,
On Tue, 2 May 2023 at 00:09, Ralph Goers wrote:
>
> 1. As noted below you tagged with red/0.1.0-rc2. You really shouldn’t be
> using rel/ as a tag for candidates. Instead use something like tools-1.0-rc2.
> rel tags are treated special by Infra and are meant for ONLY the “real”
>
One more issue. I see no reference to a web site containing release notes and a
download page. At a minimum the download page is required to send the
announcement email.
Ralph
> On May 1, 2023, at 8:41 PM, Ralph Goers wrote:
>
> Regarding item 2. I found build.log and am tailing it and I
Regarding item 2. I found build.log and am tailing it and I see that it is
downloading a ton of dependencies for running its. I am tailing the log and as
long as it keeps moving I guess it is OK.
Ralph
> On May 1, 2023, at 3:09 PM, Ralph Goers wrote:
>
> 1. As noted below you tagged with
To refine Ralph's point, once the vote passes, you create the rel/ tag
which should point to the SAME commit as the successful RC tag.
Gary
On Mon, May 1, 2023, 18:09 Ralph Goers wrote:
> 1. As noted below you tagged with red/0.1.0-rc2. You really shouldn’t be
> using rel/ as a tag for
1. As noted below you tagged with red/0.1.0-rc2. You really shouldn’t be using
rel/ as a tag for candidates. Instead use something like tools-1.0-rc2. rel
tags are treated special by Infra and are meant for ONLY the “real” release
tags (in this case 1.0).
2. I checked out the tag and ran the
10 matches
Mail list logo
