> Note: The Release CommitID should be:
https://github.com/apache/skywalking-nginx-lua/tree/9a3c5dca2f8537418b2b4887980e05aa151f0f7d

Thanks for the correction.

+1 binding
- ASC checked
- SHA exists
- SVN updated
- LICENSE and NOTICE are there
- Git tag created.

Sheng Wu 吴晟
Twitter, wusheng1108

Kai Wan <wan...@apache.org> 于2024年8月18日周日 20:45写道:
>
> +1 binding
>
> 1. GPG signatures are signed by Sheng Wu <wush...@apache.org>.
> 2 LICENSE and NOTICE exist.
> 3. The tag and version are correct.
>
> Note: The Release CommitID should be:
> https://github.com/apache/skywalking-nginx-lua/tree/9a3c5dca2f8537418b2b4887980e05aa151f0f7d
>
> —————————
> Kai Wan
> GitHub @wankai123
>
> han liu <liu...@apache.org> 于2024年8月18日周日 19:20写道:
>
> >
> > +1 binding
> >
> > 1. NOTICE and LICENSE files exist.
> > 2. .sha512 and .asc files correct.
> > 3. Tag exists.
> >
> > Sheng Wu <wu.sheng.841...@gmail.com> 于2024年8月18日周日 16:04写道:
> > >
> > > Hi all,
> > >
> > > This is a call for vote to release Apache SkyWalking Nginx LUA version 
> > > 1.0.0.
> > >
> > > Release notes:
> > >
> > > * https://github.com/apache/skywalking-nginx-lua/blob/v1.0.0/CHANGES.md
> > >
> > > Release Candidate:
> > >
> > > * https://dist.apache.org/repos/dist/dev/skywalking/nginx-lua/1.0.0/
> > > * sha512 checksums
> > > - 
> > > 8d23524c4ba753d0fc942ad1a238946fb0226865a91f664ef4ac796cecbc3deb915333e217f09a550e390cc7291b47a3dc951f0d9194734e30bf349246e574a4
> > > skywalking-nginx-lua-1.0.0-src.tgz
> > >
> > > Release Tag :
> > >
> > > * v1.0.0
> > >
> > > Release CommitID :
> > >
> > > * https://dist.apache.org/repos/dist/dev/skywalking/nginx-lua/1.0.0/
> > >
> > > Keys to verify the Release Candidate :
> > >
> > > * https://dist.apache.org/repos/dist/release/skywalking/KEYS
> > >
> > >
> > > Voting will start now (Aug 18, 2024) and will remain open for at least
> > > 72 hours, Request all PMC members to give their vote.
> > > [ ] +1 Release this package.
> > > [ ] +0 No opinion.
> > > [ ] -1 Do not release this package because....
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108

Reply via email to