jrgemignani commented on issue #2111: URL: https://github.com/apache/age/issues/2111#issuecomment-2787112555
@uhayat > what would be next step to officially release AGE 1.5.0 for PG 17? The next step is pending on others. I, unfortunately, cannot do everything - > **PG17_prepare** has been renamed to **PG17** and I created a Docker Hub **PG17** build. After that is done, and verified to be good, then the **master** branch needs to be brought in line with **PG17**, as all new work needs to be aligned with **PG17**. **PG17** can then go through a release. However, it would **not** be for version **1.5.0** as **PG17** is built off of the current **master** branch, which has a lot of work added since **1.5.0**. We would likely make **PG17** version **1.6.0**. As for the release, I can do it, but I cannot do any of the voting. After **PG17** version **1.6.0** has been released, or possibly before, we would need to release **1.6.0** for **PG16**, **PG15**, **PG14**, & **PG13**. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
