Sure, I'll write one. Best Regards, Zhiguo Wu
On 2025/04/16 00:43:42 Kengo Seki wrote: > Hi Zhiguo, > > Thank you and your collaborators for the hard work for developing BM. > Before checking the release candidate, is there any documentation > describing how to verify the RC? If not, would you write down it to > our cwiki just like > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release so > that we can review it and effectively check the RC? I think it should > include the following steps at least, but there may be necessary ones > I missed: > > * Download files under the RC directory and verify checksums > * Checkout the RC tag from the bigtop-manager repo and ensure that it > matches the extracted RC tarball > * Build the RC source and ensure that it satisfies the release > criteria of ASF such as license policy and works expected > * The release notes matche the commits included in the RC > > Regards, > > Kengo Seki <[email protected]> > > On Wed, Apr 16, 2025 at 12:05 AM Zhiguo Wu <[email protected]> wrote: > > > > Hello Community, > > > > This is a call for a vote to release Apache Bigtop Manager 1.0.0 RC0 > > > > Release note: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311420&version=12354831 > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/bigtop/bigtop-manager-1.0.0-RC0/ > > > > Git tag for the release: > > https://github.com/apache/bigtop-manager/tree/release-1.0.0-rc0 > > > > Hash for the release tag: > > 2ea1fd91062a52b983210e38f50667ce11b8ed23 > > > > The artifacts have been signed with Key > > D3D5CF25076873C9AA068C0D8F062A5450E25685, which can be found in the KEYS > > file: > > https://dist.apache.org/repos/dist/release/bigtop/KEYS > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes is reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Best Regards, > > Zhiguo Wu >
