For clarification, I believe Sonatype does not allow anything to be removed from Maven Central once it has been published. The bits are there to stay, permanently, and there are no exceptions AFAIK.
-j From: Mark Bretl <mbr...@apache.org> Date: Tuesday, October 18, 2022 at 1:14 PM To: John Blum <jb...@vmware.com> Cc: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: [DISCUSS] Move geode to the attic ⚠ External Email Unfortunately, I do think the attic is a very real possibility. @John Blum<mailto:jb...@vmware.com> Officially, I do not think we (Geode) or ASF have any type of release support policy (I searched but could not find anything), it is open-source for better or worse. VMware or any other company can pick up support if they so choose. Would have it been better for corporate sponsors to give support to a final release and give a proper send off? Yes, but we are where we are now. As for artifacts, yes they will live and remain as-is. --Mark On Tue, Oct 18, 2022 at 1:47 PM John Blum <jb...@vmware.com.invalid> wrote: How does the VMware’s non-disclosed date commitment factor into this equation? I mean, clearly the Apache Geode 1.15 release has a lifecycle and support timeline, even if the community (and a new PMC) does drive the project any further? What happens when CVEs, or critical bugs (involving data loss) are uncovered in 1.15, yet? What even is 1.15’s support timeline and overall lifecycle? I would have assumed this would minimally have been 1 year from the GA of 1.15.0. Regarding, “Geode maven artifacts would remain available from Maven Central.” This is absolutely critical and necessary for Apache Geode’s ecosystem of projects (for example, Spring for Apache Goede, such as Spring Boot and Data for Apache Geode) to continue to build and release against Apache Geode versions/bits until the end of the ecosystem project’s (e.g. SDG) support timeline. -John From: Owen Nichols <onich...@vmware.com.INVALID> Date: Tuesday, October 18, 2022 at 11:50 AM To: dev@geode.apache.org<mailto:dev@geode.apache.org> <dev@geode.apache.org<mailto:dev@geode.apache.org>> Subject: Re: [DISCUSS] Move geode to the attic ⚠ External Email Once moved to the attic, it sounds like: * The geode github repo would become read-only (but remain world-readable in perpetuity). * Geode would no longer be available for download on the geode download site or mirrors (but still available in releases tab in github). * Geode maven artifacts would remain available from mavencentral. * Geode homebrew formula would no longer be installable. * Unsure whether apachegeode/geode docker image would remain available? * Geode confluence wiki would become read-only. * It sound like the user mailing list may be able to remain active? Since no further release are possible without at least 3 active PMC members to provide the requisite 3 approving PMC votes, the Attic sounds like the best possible way to leave things. From: Dan Smith <dasm...@vmware.com.INVALID> Date: Tuesday, October 18, 2022 at 11:12 AM To: dev@geode.apache.org<mailto:dev@geode.apache.org> <dev@geode.apache.org<mailto:dev@geode.apache.org>> Subject: [DISCUSS] Move geode to the attic ⚠ External Email Hi folks, Unfortunately, it is time to consider moving Geode to the Apache attic. After VMware's announcement that it will stop contributing to Geode, we've tried in the last couple months to recruit additional contributors to continue supporting the project [1]. However, this last week there was a PMC role call on the private list and it appears we will only have one active PMC member after the VMware folks completely leave. I think at this point the responsible thing to do is dissolve the Geode PMC and move the project to the attic, unless some new contributors suddenly show up. We need a minimum of 3 PMC members to keep the project viable. This is not yet a vote. I'll let this discussion run this week and start a vote next week. I believe even if we vote to dissolve the project and move to the attic, the soonest that process would start would be after the November board meeting [2]. Thanks, -Dan [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fd88byb42gm5wplzqwkgywg3w9vtj64dr&data=05%7C01%7Cjblum%40vmware.com%7C482d2bf794ef46bd167508dab1399813%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638017158176942172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eRrcPuf2Ccnkj1SIOWs%2B%2BRwjgiJch0T%2FnbYt2NMt78A%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fd88byb42gm5wplzqwkgywg3w9vtj64dr&data=05%7C01%7Cjblum%40vmware.com%7C12db61d4534c407f607108dab145506c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638017208525885518%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=o8TqE35x4%2F%2B9wq6wpbmBAOMOS%2BbfGkDDUZrfGBFfOLI%3D&reserved=0> [2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fattic.apache.org%2Fprocess.html&data=05%7C01%7Cjblum%40vmware.com%7C482d2bf794ef46bd167508dab1399813%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638017158176942172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PcH23xVCIid04KbsJnbJVKMZ2%2BcZyHWEov7hVsD0OjM%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fattic.apache.org%2Fprocess.html&data=05%7C01%7Cjblum%40vmware.com%7C12db61d4534c407f607108dab145506c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638017208526041751%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8EFV19HPc3Co0BCSW9pY1KVoqitQYVCaXBUXsClEAF8%3D&reserved=0> ________________________________ ⚠ External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.
