Hi EJ, This plan sounds good to me. Thanks for volunteering!
I have created https://github.com/apache/polaris/issues/4579, as the release workflow and documentation need to be updated. I am currently working on this, and it should be considered a release blocker. Additionally, you will need the assistance of a PMC member to complete the post-vote release steps. I will be happy to help you with that process. Regards, JB On Fri, May 29, 2026 at 9:16 PM EJ Wang <[email protected]> wrote: > > Hi all, > > I would like to volunteer as the release manager for Apache Polaris 1.6.0. > > I am thinking about targeting Friday, June 26, 2026 for the release, > assuming the community agrees and we do not have blocking issues by then. > > To start planning, could folks please share if there are any: > - release blockers for 1.6.0 > - must-have PRs that should be included > - timing concerns around the proposed date > - areas where you would like to help validate the release candidate > > Based on the previous 1.5.0 release flow, my rough plan is: > - collect blockers and must-have PRs over the next couple of weeks > - start converging the scope around mid-June > - prepare the changelog/release notes and cut the first RC around June 20 > - keep the vote open for at least 72 hours > - publish and announce the release around June 26 if the vote passes > > I will also keep an eye on release workflow/artifact validation, including > source artifacts, Maven artifacts, Docker images, Helm chart, Python > package, and the website/downloads page. > > Please let me know if this timeline sounds reasonable, or if there are > concerns I should account for. > > Thanks, > -ej
