+1 Verified the following things:
- Checked NOTICE, DISCLAIMER, README, and CHANGELOG - Verified signature - Build from source using make - Run unit test using make test - Run some sample workloads, roughly went over the logs and k8s messages - Verified the basic UI functionalities - Inspected the docker images and verified the commit SHAs Thanks On Thu, Jan 13, 2022 at 4:53 PM Wilfred Spiegelenburg <[email protected]> wrote: > +1 > > Checked the following: > * no unexpected binaries or files > * signature confirmed > * hash confirmed > * build from source > * startup and run the tests > * deployed into kind 1.22.4 using helm charts and local build > * checked REST calls: logLevel, healthcheck, and statedump > * checked Web UI > > On Fri, 14 Jan 2022 at 05:45, Craig Condit <[email protected]> wrote: > > > > Hello everyone, > > > > I’d like to call a vote for releasing Apache YuniKorn (incubating) > 0.12.2 RC2. > > > > The release artifacts have been uploaded here: > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc2/ < > https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.12.2-rc2/> > > > > My public key is located here: > https://downloads.apache.org/incubator/yunikorn/KEYS < > https://downloads.apache.org/incubator/yunikorn/KEYS> > > > > JIRA issues that have been resolved in this release: > https://issues.apache.org/jira/issues/?filter=12351270 < > https://issues.apache.org/jira/issues/?filter=12351270> > > > > Since only changes to the release repo were necessary for RC2, tags > remain at 0.12.2-1 in code, only the release repo has been tagged 0.12.2-2. > Post-release, all repos will be tagged 0.12.2 for consistency. > > > > Please review and vote. The vote will be open for at least 72 hours and > closes on Tuesday, January 18 2022, 1pm PDT. > > > > [ ] +1 Approve > > [ ] +0 No opinion > > [ ] -1 Disapprove (and the reason why) > > > > > > Thank you, > > Craig > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
