recreating only the source tarball should be enough if we cut RC1.
Or, isn't it enough to add a notice and workaround to the release page
on cwiki, which is supposed to be published such as
https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+1.5.0+Release?
I'm OK to avoid cutting RC1 given that binary packages have no issue.
Thanks,
Masatake Iwasaki
On 2021/10/20 10:14, Kengo Seki wrote:
Thank you for finding this and testing all packages, Masatake!
recreating only the source tarball should be enough if we cut RC1.
Or, isn't it enough to add a notice and workaround to the release page
on cwiki, which is supposed to be published such as
https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+1.5.0+Release?
Kengo Seki <[email protected]>
On Wed, Oct 20, 2021 at 10:04 AM Masatake Iwasaki
<[email protected]> wrote:
I filed BIGTOP-3589 related to source tarball of RC0.
I got no issue on packaging other products from the source tarball (on CentOS 8
x86_64 and Ubuntu 18.04 x86_64).
Since the fix of BIGTOP-3589 does not affect binary packages built from the RC0,
recreating only the source tarball should be enough if we cut RC1.
On 2021/10/19 19:51, Masatake Iwasaki wrote:
Thanks for putting this up, Kengo.
I filed BIGTOP-3589 related to source tarball of RC0.
Masatake Iwasaki
On 2021/10/19 8:16, Kengo Seki wrote:
This is the vote for release 3.0.0 of Apache Bigtop.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311420&version=12349352
The vote will be going for at least 72 hours and will be closed on Thursday,
October 21st, 2021 at 17:00 PDT. Please download, test and vote with
[ ] +1, accept RC0 as the official 3.0.0 release of Apache Bigtop
[ ] +0, I don't care either way,
[ ] -1, do not accept RC0 as the official 3.0.0 release of Apache
Bigtop, because...
Source and binary files:
https://dist.apache.org/repos/dist/dev/bigtop/bigtop-3.0.0-RC0/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachebigtop-1031
The git tag to be voted upon is release-3.0.0
Bigtop's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/release/bigtop/KEYS
You can see the results of packaging, deployment and smoke tests on
the CI environment in the following URLs.
Some builds had to be retried several times since some of our tests
are flaky, but all of them succeeded at last.
(I ran the smoke tests for all distros on x86_64. Regarding aarch64 and ppc64le,
I ran them only for CentOS and Debian on the former and for Fedora and
Ubuntu on the latter,
since our computation resource is respectively limited.)
https://ci.bigtop.apache.org/view/Releases/job/Bigtop-3.0.0/
https://ci.bigtop.apache.org/view/Test/job/Bigtop-3.0.0-smoke-tests/
Kengo Seki <[email protected]>
