Thanks! Then I'll create a new build job for the 3.0.1 release on Jenkins.
I'm also going to stop the periodic execution of the trunk build
temporarily, because the computational resources are limited. But if you'd
like to run it for some reason (e.g., BIGTOP-3644 - thanks a lot for
addressing it!)
Hi Kengo and Masatake,
Definitely 3.0.1 is ok! Having new packages out with the log4j fix is
enough in my opinion, and then 3.1 can follow later on with more
changes.
Thanks!
On Tue, Feb 22, 2022 at 3:33 AM Kengo Seki wrote:
>
> I'd also release 3.0.1 based on branch-3.0 first, since 3.1.0 drop
I'd also release 3.0.1 based on branch-3.0 first, since 3.1.0 drops Debian
9 (BIGTOP-3629) but its users may need a patch release for addressing
Log4Shell vulnabilites.
Is it OK for you, Luca? And if it's OK, do you have any fixes to be
included in 3.0.1 (Debian 11 support, for example)?
Kengo Sek
Hi Luca,
How about releasing 3.0.1 first?
I think issues under BIGTOP-3613 are landed to both master and branch-3.0.
I want to BIGTOP-3606 be in 3.1, it is not yet resolved.
After Bigtop 3.0.1, we can release Bigtop 3.1.0 even without BIGTOP-3606.
If it takes more time in Hadoop side, we can add
Hi, I find that the bgtp-ambari-mpack is not apply the bigtop 3.x, but it
work well with bigtop 1.5.
Luca Toscano 于 2022年2月21日周一 16:08写道：
> Hi everybody,
>
> I am wondering if it would be good to release 3.1 during the coming
> weeks to address the log4j vulnerabilities. Thoughts? No idea how
>
Hi everybody,
I am wondering if it would be good to release 3.1 during the coming
weeks to address the log4j vulnerabilities. Thoughts? No idea how
tough the process is, but I'll help if needed!
Luca
