+1 Since 3.3.0 is not released yet, I think it's better if we could remove the code from branch-3.3 also.
Best Regards, Zhiguo Wu ---- Replied Message ---- | From | Masatake Iwasaki<iwasak...@oss.nttdata.com> | | Date | 5/29/2024 18:52 | | To | dev@bigtop.apache.org<dev@bigtop.apache.org> | | Subject | [DISCUSS] Drop GPDB from Bigtop | Hi Bigtop developers, Packaging of GPDB failed due to 404. Not Found (HTTP status code: 404, URL: https://github.com/greenplum-db/gpdb/archive//7.1.0.tar.gz) The GitHub repository of GPDB seems to be moved to gpdb-archive and it is read only now. https://github.com/greenplum-db/gpdb-archive https://news.ycombinator.com/item?id=40507691 While I can see no details about the archiving, I see no reason to keep bundling it in Bigtop. I believe no Bigtop user is interested in GPDB since there was no contribution around GPDB for years. I'm going to drop the GPDB even from 3.3.0 which is in release process. We can release 3.3.0 even without patching current code base. We just need to declare that it is dropped and excluding the GPDB from CI build. Thanks, Masatake Iwasaki
