Hey Ed, Thanks for taking on the role of Release Manager for Cloudberry 2.0.0. Your experience with Apache projects will be a great asset in guiding this release forward.
A few thoughts regarding the upcoming release: 1. PRs to Consider for Inclusion I have 3 PRs that I'd like to see included in this release, and would greatly appreciate help from the community in reviewing them. #1053, #1004, #929 It might be helpful if contributors could also list any PRs they hope to include, so we can prioritize reviews accordingly. 2. Feature Requests from the Community I’ve collected some feedback and feature requests from community members and wanted to reshare them here for visibility: * Besides RPM packages for EL 8/9, will we offer .deb packages for Ubuntu? * Is there any plan to offer an official Docker image for this release? A quick note on the first item: @leborchuk has contributed PRs to set up the Ubuntu dev/test container and support the Debian package generation. I've helped test the Ubuntu dev/test container PR and it works well now; that would be better to proceed with it if others can also help verify, so @leborchuk can proceed with his Debian package work.[1][2] I would also like to help test if needed. Looking forward to the first Apache release for Cloudberry! [1] https://github.com/apache/cloudberry-devops-release/pull/13 [2] https://github.com/apache/cloudberry-devops-release/pull/15 Best, Dianjin Wang On Sun, Apr 20, 2025 at 4:36 PM Ed Espino <esp...@apache.org> wrote: > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org For additional commands, e-mail: dev-h...@cloudberry.apache.org
