full teardown/rebuild of cdn-in-a-box builds/runs successfully and did some
light testing through TP.

+1

On Fri, Mar 26, 2021 at 11:22 AM Zach Hoffman <[email protected]> wrote:

> +1, the components build and work as expected.
>
> Traffic Ops API v3 tests can sometimes fail with a message like
>    servers_test.go:342: Expected 200 status code, got 304
> but that is a bug in the API tests themselves (similar to what
> https://github.com/apache/trafficcontrol/pull/4851 fixes), and Traffic Ops
> itself work as intended.
>
> -Zach
>
> On Mon, Mar 22, 2021 at 1:16 PM ocket 8888 <[email protected]> wrote:
>
> > Hello All,
> >
> > I've prepared a release for v5.1.1-RC0
> >
> > 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 5.1.0:
> >
> >
> https://github.com/apache/trafficcontrol/compare/RELEASE-5.1.0...RELEASE-5.1.1-RC0
> >
> > This corresponds to git:
> > Hash: 94539b43f596d58a71505eb3017d4cdcafe769b6
> > Tag: RELEASE-5.1.1-RC0
> >
> > Which can be verified with the following: git tag -v RELEASE-5.1.1-RC0
> >
> > My code signing key is available here:
> >
> >
> https://keys.gnupg.net/pks/lookup?search=0xF5D560A373B76FA302A95DBFCDFE430685982C95&fingerprint=on&op=index
> >
> > 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/5.1.1/RC0
> >
> > Thanks!
> > ocket8888 [email protected]
> >
>

Reply via email to