You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Sean Busbey <sb...@apple.com.INVALID> on 2022/03/08 21:37:02 UTC
Missing tag for 1.9.0 release
Hi!
We’re missing a git tag for the 1.9.0 release. Could someone push one?
From looking at the VOTE threads, I believe this git commit is what was voted on:
> d4fcab4f501d41597bc616921329a4339f73585e
That’s the current head of branch-1.9.
I see that prior releases were named like “release-1.8.0”. To get the advantage of default git protections provided by ASF infra release tags have to start with “rel/“. So if we could either name the tag “rel/1.9.0” or “rel/release-1.9.0” that would be best.
Re: Missing tag for 1.9.0 release
Posted by Ralph Goers <ra...@dslextreme.com>.
I wouldn’t be surprised if the ‘real’ thing came about after the last Flume release. I know we went back and tagged all the old Log4j releases after that came out.
I will see if I can’t get a tag applied to the correct place.
Ralph
> On Mar 8, 2022, at 2:37 PM, Sean Busbey <sb...@apple.com.INVALID> wrote:
>
>
> Hi!
>
> We’re missing a git tag for the 1.9.0 release. Could someone push one?
>
> From looking at the VOTE threads, I believe this git commit is what was voted on:
>
>> d4fcab4f501d41597bc616921329a4339f73585e
>
> That’s the current head of branch-1.9.
>
>
> I see that prior releases were named like “release-1.8.0”. To get the advantage of default git protections provided by ASF infra release tags have to start with “rel/“. So if we could either name the tag “rel/1.9.0” or “rel/release-1.9.0” that would be best.
>
>