Hi all, As we prepare for the next release of Apache Cloudberry (Incubating), I’d like to volunteer to serve as the Release Manager (RM) for the upcoming 2.0.0 release.
For those who may be new to the Apache process: the Release Manager is a community volunteer who coordinates the technical and procedural aspects of a release. This includes tagging the release, assembling the source artifacts, verifying licensing and compliance (e.g., via Apache RAT), initiating votes on the dev@ and general@ mailing lists, and completing post-vote publication steps. While the RM helps move the release forward, all decisions are made openly and collaboratively. I’ve previously served in this role on other Apache projects, including Apache MADlib and Apache HAWQ (now in the Attic), so I’m familiar with the overall release process. That said, I’ll be refreshing my understanding of the specific requirements for incubating projects as we go, and will ensure we follow ASF Incubator policy throughout. For anyone interested in reviewing the process or following along, the project’s Wiki includes our release procedures and checklists: https://github.com/apache/cloudberry/wiki I'll be documenting each step, so others can get familiar with the process or jump in to assist. If there are any questions or concerns, please feel free to raise them here. Looking forward to working with everyone on this. Best, -=e -- Ed Espino Apache Cloudberry (Incubating) & MADlib
