Okay I think I find one issue. So -1. The code literally has RC in version.py. if we just literally move this source to releases then this won't fly. I'll need to change this. Please continue to verify. I am assuming there might be one or two more things to correct. Will create another RC candidate and vote after this one concludes.
On Sat, Sep 13, 2025, 10:26 PM Stefan Krawczyk <[email protected]> wrote: > Hi all, > > This is a call for a vote on releasing Apache hamilton 1.89.0-incubating, > release candidate 0. > > This release includes the following changes: > - Too many to list. Will build tooling to help automate this. > > The artifacts for this release candidate can be found at: > https://dist.apache.org/repos/dist/dev/incubator/hamilton/1.89.0-RC0 > > The Git tag to be voted upon is: > v1.89.0 (based off of this PR > <https://github.com/apache/hamilton/pull/1378>) > > The release hash (can use git tag) will be provided once we merge a commit > with version 1.89.0 to main. > > Release artifacts are signed with the following key: > > 25E1C6FA3B71D486DC46BD3630C8F2B2CC329C0B > > The KEYS file is available at: > https://downloads.apache.org/incubator/hamilton/KEYS > > Please download, verify, and test the release candidate. > > The vote will run for a minimum of 72 hours. > Please vote: > > [ ] +1 Release this package as Apache hamilton 1.89.0-incubating > [ ] +0 No opinion > [ ] -1 Do not release this package because... (Please provide a reason) > > On behalf of the Apache Hamilton PPMC, > > Stefan Krawczyk > > P.S. @Mentors with our project, we literally commit the version into the > source code. This means that we will build releases off of branches and > then if all good merge into main. Is that kosher? or not? >
