> is there any reason to keep master branch closed? I didn't want to make master branch too out of sync with 1.25.0 release. Unfortunately I was not yet given permissions for SVN dist repository which prevents me from finalizing the release.
That being said, keeping master frozen for too long is not optimal. I will merge existing release branch today and hopefully finalize 1.25 next week independently. Sorry for the inconvenience. On Sat, Aug 15, 2020 at 2:47 PM Julian Hyde <[email protected]> wrote: > Andrei, > > Now the release is final, is there any reason to keep master branch closed? > > (Usually we push branch-x.x to master and re-open commits as soon as > the release vote passes. Amendments to release notes, if necessary, > can happen later.) > > Julian > > On Wed, Aug 12, 2020 at 11:13 AM Andrei Sereda <[email protected]> wrote: > > > > Thanks to everyone who has tested the release candidate and given their > > comments and votes. > > > > The tally is as follows. > > > > 4 binding +1s: > > * Francis Chuang > > * Michael Mior > > * Haisheng Yuan > > * Julian Hyde > > > > 7 non-binding +1s: > > * Enrico Olivelli > > * Rui Wang > > * chunwei > > * Ruben Q L > > * Anton Haidai > > * xzh > > * Andrei Sereda > > > > No 0s or -1s. > > > > Therefore I am delighted to announce that the proposal to release Apache > > Calcite 1.25.0 has passed. > > > > Thanks everyone. We’ll now roll the release out to the mirrors. > > > > I will also update release notes (in separate commit) to better > > reflect 1.25.0 changes. > > > > Please refrain from modifying master until release is over. Separate > > notification will be sent once commits are allowed. > > > > Andrei >
