+1, everything is looking good so far.

- Rawlin

On Tue, Jun 16, 2020 at 11:24 AM Jeremy Mitchell <[email protected]> wrote:
>
> +1 for me as well. We have been validating changes as they come in as well
> as performing additional release validation in our staging environment.
> Plus, as Dave mentioned, 4.1 is currently in our production environment.
>
> Jeremy
>
> On Tue, Jun 16, 2020 at 8:11 AM Dave Neuman <[email protected]> wrote:
>
> > +1, we have this running in production now.
> >
> > On Wed, Jun 10, 2020 at 5:51 PM Rawlin Peters <[email protected]> wrote:
> >
> > > Hello All,
> > >
> > > I've prepared a release for v4.1.0-RC2
> > >
> > > The vote is open for at least 72 hours and passes if a majority of at
> > > least 3 +1 PMC votes are cast.
> > >
> > > [ ] +1 Approve the release
> > >
> > > [ ] -1 Do not release this package because ...
> > >
> > > Changes since 4.0.0:
> > >
> > >
> > https://github.com/apache/trafficcontrol/compare/RELEASE-4.0.0...RELEASE-4.1.0-RC2
> > >
> > > This corresponds to git:
> > > Hash: 1e34ccd8a15c853902a154600efc60466d5736ca
> > > Tag: RELEASE-4.1.0-RC2
> > >
> > > Which can be verified with the following: git tag -v RELEASE-4.1.0-RC2
> > >
> > > My code signing key is available here:
> > > http://keys.gnupg.net/pks/lookup?search=0x8A0712500C70C06E&op=vindex
> > >
> > > Make sure you refresh from a key server to get all relevant signatures.
> > >
> > > The source .tgz file, pgp signature (.asc signed with my key from
> > > above), and sha512 checksums are provided here:
> > >
> > > https://dist.apache.org/repos/dist/dev/trafficcontrol/4.1.0/RC2
> > >
> > >
> > > Thanks!
> > > Rawlin Peters [email protected]
> > >
> >

Reply via email to