Thanks Andrei! -- Michael Mior mm...@apache.org
Le sam. 22 août 2020 à 15:08, Andrei Sereda <and...@sereda.cc> a écrit : > > INFRA-20681 was resolved. > > I have published the artifacts to SVN dist area. > > Will update static site and send an announcement shortly. > > On Fri, Aug 21, 2020 at 5:37 PM Andrei Sereda <and...@sereda.cc> wrote: > > > Hello, > > > > I'm still waiting for INFRA-20681 [1] to be resolved to publish 1.25.0 > > artifacts to SVN. If some of you know different channels to speed up the > > resolution please let me know. > > > > [1] https://issues.apache.org/jira/browse/INFRA-20681 > > > > On Sun, Aug 16, 2020 at 12:58 PM Andrei Sereda <and...@sereda.cc> wrote: > > > >> 1.25 branch has been merged. > >> > >> Master is unlocked now. I have also sent separate notification. > >> > >> On Sat, Aug 15, 2020 at 7:07 PM Julian Hyde <jh...@apache.org> wrote: > >> > >>> You can "git push origin calcite-1.25.0-rc0:master" and then re-open > >>> master. I don't think there's any reason to wait. Since the release > >>> vote has passed, we know that 68b02dfd4 is going to end up on master. > >>> And we don't mind if people make intervening commits before you tweak > >>> the release notes or whatever. > >>> > >>> On Sat, Aug 15, 2020 at 3:12 PM Andrei Sereda <and...@sereda.cc> wrote: > >>> > > >>> > > 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 <jh...@apache.org> 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 <and...@sereda.cc> > >>> 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 > >>> > > > >>> > >>
