-1 looks like privlevel is still being referenced in the v5 api but it was fixed with this commit:
https://github.com/apache/trafficcontrol/commit/5081509d5f0b42f5c50621deb07521c7db6d863a On Mon, Sep 25, 2023 at 4:23 PM R S <[email protected]> wrote: > Hello All, > > I've prepared a release for 8.0.0-RC2. Changes since RELEASE-8.0.0-RC1: > > https://github.com/apache/trafficcontrol/compare/v8.0.0-rc1...v8.0.0-rc2 > > > https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC2/CHANGELOG.md > > The artifacts are available for download at: > https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.0/RC2/ > > BLAKE2 checksum: > > > eb58add53ae87da2edcbef6fd556ea8e1203e82e1b69322572b8ae641e32fc5892529b29dea553ed3d2fbf7feed7ed3689157ac4c8a6e62c1504d4250bb554b1 > > SHA512 checksum: > > 5e11dc0918e5bfc8bd127deaaba96c97d19152cb06b56d2aef3255f43eb11006ab5c12f1e272118b99b32f0c09bb292eb212fc31d7b3b123950c5f74bb4d1cd8 > > This corresponds to git refs: > > Hash:3a5c72f0665c449c1e679ab97271ff0272b8e5cf > Tag: RELEASE-8.0.0-RC2 > > Which can be verified with the following command: > > $ git tag -v RELEASE-8.0.0-RC2 > > All code signing keys are available here: > > https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS > > Make sure you refresh from a key server to get all relevant signatures. > > The vote is open until 22:00 UTC on Thursday, September 28 and passes > if a majority of at least 3 +1 PMC votes are cast. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks! > Rima Shah > > [email protected] >
