Re: [VOTE] Release apache-calcite-1.27.0 (release candidate 0)
Thanks for pushing through this massive release, Stamatis! My vote is: +1 - Verified GPG signature - OK - Verified SHA512 - OK - Checked release notes - OK - Ran tests (gradle test) - OK - Spot checked Nexus artifacts - OK Environment: Gradle 6.8.3 docker container in WSL2 (Ubuntu 20.04) on Windows 10 21h1 > docker version Client: Docker Engine - Community Cloud integration: 1.0.14 Version: 20.10.6 API version: 1.41 Go version:go1.13.15 Git commit:370c289 Built: Fri Apr 9 22:46:45 2021 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.6 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: 8728dd2 Built:Fri Apr 9 22:44:56 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.4 GitCommit:05f951a3781f4f2c1911b05e61c160e9c30eaa8e runc: Version: 1.0.0-rc93 GitCommit:12644e614e25b05da6fd08a38ffa0cfe1903fdec docker-init: Version: 0.19.0 GitCommit:de40ad0 > gradle -v Gradle 6.8.3 Build time: 2021-02-22 16:13:28 UTC Revision: 9e26b4a9ebb910eaa1b8da8ff8575e514bc61c78 Kotlin: 1.4.20 Groovy: 2.5.12 Ant: Apache Ant(TM) version 1.10.9 compiled on September 27 2020 JVM: 1.8.0_282 (AdoptOpenJDK 25.282-b08) OS: Linux 5.4.72-microsoft-standard-WSL2 amd64 > java -version openjdk version "1.8.0_282" OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_282-b08) OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.282-b08, mixed mode) Francis On 1/06/2021 1:28 am, Stamatis Zampetakis wrote: Hi all, I have created a build for Apache Calcite 1.27.0, release candidate 0. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.27.0-rc0/site/_docs/history.md The commit to be voted upon: https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=60f07118f31776462ea35ffdaa1f46c633251f69 Its hash is 60f07118f31776462ea35ffdaa1f46c633251f69 The artifacts to be voted on are located here: https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.27.0-rc0 (revision 48026) The hashes of the artifacts are as follows: 6e81b8b155cbece67d5b0c3f81ee3cf086da7e28b95d20ad8d819080b6caaf03f021af00339e9d70a2d7b1a0b27a86fac14ad94c0a2967a12991fb9170dee4d3 *apache-calcite-1.27.0-src.tar.gz A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecalcite-1115/org/apache/calcite/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/zabetak.asc https://www.apache.org/dist/calcite/KEYS To create the jars and test Apache Calcite: "gradle build" (requires an appropriate Gradle/JDK installation). Please vote on releasing this package as Apache Calcite 1.27.0. The vote is open for the next 72 hours and passes if a majority of at least three +1 PMC votes are cast. [ ] +1 Release this package as Apache Calcite 1.27.0 [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... Here is my vote: +1 (binding) Stamatis
Re: Fwd: [NOTICE] Git web site publishing to be done via .asf.yaml only as of July 1st
+1 I think that's all we need to do. Thanks Michael! :) Wish they used better contrasting colors on https://infra-reports.apache.org/site-source/ though. The green and yellow rows all look white to me! On 1/06/2021 12:23 am, Michael Mior wrote: It seems like Calcite is affected by this change. I believe all that is necessary is to add .asf.yml to the calcite-site repository with the following contents: publish: whoami: master We have plenty of time to make the change, so if there are no objections or concerns, I'll commit this in the next week or two. -- Michael Mior mm...@apache.org -- Forwarded message - De : Daniel Gruno Date: lun. 31 mai 2021 à 09:41 Subject: [NOTICE] Git web site publishing to be done via .asf.yaml only as of July 1st To: Users TL;DR: if your project web site is kept in subversion, disregard this email please. If your project web site is using git, and you have not deployed it via .asf.yaml, you MUST switch before July 1st or risk your web site goes stale. Dear Apache projects, In order to simplify our web site publishing services and improve self-serve for projects and stability of deployments, we will be turning off the old 'gitwcsub' method of publishing git web sites. As of this moment, this involves 120 web sites. All web sites should switch to our self-serve method of publishing via the .asf.yaml meta-file. We aim to turn off gitwcsub around July 1st. ## How to publish via .asf.yaml: Publishing via .asf.yaml is described at: https://s.apache.org/asfyamlpublishing You can also see an example .asf.yaml with publishing and staging profiles for our own infra web site at: https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml In short, one puts a file called .asf.yaml into the branch that needs to be published as the project's web site, with the following two-line content, in this case assuming the published branch is 'asf-site': publish: whoami: asf-site It is important to note that the .asf.yaml file MUST be present at the root of the file system in the branch you wish to publish. The 'whoami' parameter acts as a guard, ensure that only the intended branch is used for publishing. ## Is my project affected by this? The quickest way to check if you need to switch to a .asf.yaml approach is to check out site source page at https://infra-reports.apache.org/site-source/ - if your site is listed in yellow, you will need to switch. This page will also tell you which branch you are currently publishing as your web site. This is (should be) the branch that you must add a .asf.yaml meta file to. The web site source list updates every hour. If your project site appears in green, you are already using .asf.yaml for publishing and do not need to make any changes. ## What happens if we miss the deadline? If you miss the deadline, don't fret. Your site will of course still remain online as is, but new updates will not appear till you create/edit the .asf.yaml and set up publishing. ## Who do we contact if we have questions? Please contact us at us...@infra.apache.org if you have any additional questions. With regards, Daniel on behalf of ASF Infra.
Re: [VOTE] Release apache-calcite-1.27.0 (release candidate 0)
Hi Stamatis, thanks a lot for the release candidate, I will check it asap in more details. In the meantime I have just noticed in the release notes that the date is off (the year): 1.27.0 / 2020-06-XX Best regards, Alessandro On Mon, 31 May 2021 at 17:29, Stamatis Zampetakis wrote: > > Hi all, > > I have created a build for Apache Calcite 1.27.0, release > candidate 0. > > Thanks to everyone who has contributed to this release. > > You can read the release notes here: > https://github.com/apache/calcite/blob/calcite-1.27.0-rc0/site/_docs/history.md > > The commit to be voted upon: > https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=60f07118f31776462ea35ffdaa1f46c633251f69 > > Its hash is 60f07118f31776462ea35ffdaa1f46c633251f69 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.27.0-rc0 > (revision 48026) > > The hashes of the artifacts are as follows: > 6e81b8b155cbece67d5b0c3f81ee3cf086da7e28b95d20ad8d819080b6caaf03f021af00339e9d70a2d7b1a0b27a86fac14ad94c0a2967a12991fb9170dee4d3 > *apache-calcite-1.27.0-src.tar.gz > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachecalcite-1115/org/apache/calcite/ > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/zabetak.asc > https://www.apache.org/dist/calcite/KEYS > > To create the jars and test Apache Calcite: "gradle build" (requires an > appropriate Gradle/JDK installation). > > Please vote on releasing this package as Apache Calcite 1.27.0. > > The vote is open for the next 72 hours and passes if a majority of at > least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Calcite 1.27.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > > Here is my vote: > > +1 (binding) > > Stamatis
[VOTE] Release apache-calcite-1.27.0 (release candidate 0)
Hi all, I have created a build for Apache Calcite 1.27.0, release candidate 0. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.27.0-rc0/site/_docs/history.md The commit to be voted upon: https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=60f07118f31776462ea35ffdaa1f46c633251f69 Its hash is 60f07118f31776462ea35ffdaa1f46c633251f69 The artifacts to be voted on are located here: https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.27.0-rc0 (revision 48026) The hashes of the artifacts are as follows: 6e81b8b155cbece67d5b0c3f81ee3cf086da7e28b95d20ad8d819080b6caaf03f021af00339e9d70a2d7b1a0b27a86fac14ad94c0a2967a12991fb9170dee4d3 *apache-calcite-1.27.0-src.tar.gz A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecalcite-1115/org/apache/calcite/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/zabetak.asc https://www.apache.org/dist/calcite/KEYS To create the jars and test Apache Calcite: "gradle build" (requires an appropriate Gradle/JDK installation). Please vote on releasing this package as Apache Calcite 1.27.0. The vote is open for the next 72 hours and passes if a majority of at least three +1 PMC votes are cast. [ ] +1 Release this package as Apache Calcite 1.27.0 [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... Here is my vote: +1 (binding) Stamatis
Re: [DISCUSS] Towards Calcite 1.27.0
Hi all,
I am currently preparing the first release candidate for 1.27.0.
Please do not commit to master, until further notice.
Best,
Stamatis
On Fri, May 28, 2021 at 4:15 PM Stamatis Zampetakis
wrote:
> I did a pass over the JIRA issues marked for 1.27.0 release.
> I moved some that were promising but not close to be resolved in 1.28.0
> and for others that there was not much (or any) progress I removed the fix
> version tag.
> After the cleanup it seems that there are three/four issues [1] that could
> possibly go in rather fast (in the next day or so).
> I left some comments under each case so I am waiting for feedback to
> prepare the first release candidate.
>
> Please let me know ASAP if there is some other issue that is not in the
> list [1] and needs to be in 1.27.0.
>
> Best,
> Stamatis
>
> [1]
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950
>
> On Mon, May 24, 2021 at 10:10 PM Ruben Q L wrote:
>
>> I'll pick 3-5 PRs too.
>>
>> Ruben
>>
>> On Mon, May 24, 2021 at 8:34 PM Julian Hyde
>> wrote:
>>
>> > Thanks Rui! Just pick 5 PRs that look interesting to you, and assign the
>> > JIRA to yourself (as active reviewer). If you need help/advice, mention
>> > people in the JIRA comments.
>> >
>> > We need 4 more volunteers…
>> >
>> > Julian
>> >
>> >
>> > > On May 24, 2021, at 11:28 AM, Rui Wang wrote:
>> > >
>> > > Please tag me on PRs that you need my help. I will check those soon.
>> > >
>> > >
>> > > -Rui
>> > >
>> > > On Mon, May 24, 2021 at 11:06 AM Julian Hyde
>> wrote:
>> > >
>> > >> We still need 5 committers to review 5 PRs each. Please reply to this
>> > >> email to volunteer.
>> > >>
>> > >> On Fri, May 21, 2021 at 3:41 PM Stamatis Zampetakis <
>> zabe...@gmail.com>
>> > >> wrote:
>> > >>>
>> > >>> I agree with Julian, we should get the 1.27.0 out as soon as
>> possible.
>> > >>>
>> > >>> I can try to prepare RC0 between the 28 and 30 of May, if people
>> agree
>> > on
>> > >>> this.
>> > >>> Alternatively, I will have a bit more time around 17 to 20 of June.
>> > >>>
>> > >>> I will try to get 2-3 PRs in before starting the RC.
>> > >>>
>> > >>> Best,
>> > >>> Stamatis
>> > >>>
>> > >>>
>> > >>> On Fri, May 21, 2021 at 9:15 PM Julian Hyde
>> wrote:
>> > >>>
>> > Now Avatica 1.18 has been released (thanks, Francis!) we should
>> press
>> > >> on
>> > with Calcite 1.27.
>> >
>> > Who is release manager? Stamatis, You volunteered to be release
>> > manager
>> > for 1.27 [1] but I would be happy to jump in. Let me know.
>> >
>> > There is a backlog of PRs that look good enough to go into 1.27.
>> How
>> > to
>> > tackle these? I think we need 4 or 5 committers to each look over
>> 4 or
>> > >> 5
>> > PRs in the next few days. Please reply to this email if you are
>> > >> prepared to
>> > help.
>> >
>> > Julian
>> >
>> > [1]
>> >
>> > >>
>> >
>> https://lists.apache.org/thread.html/re5702a648df18f56e786d770cdce86101164ae419eee94ae947652d4%40%3Cdev.calcite.apache.org%3E
>> >
>> > On 2021/03/09 14:29:16, Stamatis Zampetakis
>> > wrote:
>> > > Many thanks for moving this forward Julian, much appreciated.
>> > >
>> > > At the moment the main blocker is the Avatica release ([1,2])
>> that in
>> > turn
>> > > waits for CALCITE-4503 [3].
>> > > It would be great if somebody has some cycles to review and merge
>> the
>> > > respective PR [4].
>> > >
>> > > Best,
>> > > Stamatis
>> > >
>> > > [1] https://issues.apache.org/jira/browse/CALCITE-4528
>> > > [2] https://issues.apache.org/jira/browse/CALCITE-4488
>> > > [3] https://issues.apache.org/jira/browse/CALCITE-4503
>> > > [4] https://github.com/apache/calcite-avatica/pull/138
>> > >
>> > > On Sun, Feb 28, 2021 at 2:22 AM Julian Hyde
>> > >> wrote:
>> > >
>> > >> Vladimir,
>> > >>
>> > >> Thanks for finding this bug. Please log it.
>> > >>
>> > >> I don't intend to fix any more bugs in this area before 1.27. It
>> > >> has
>> > >> been a huge effort on my part, and I have not received any help
>> > >> from
>> > >> anyone.
>> > >>
>> > >> Julian
>> > >>
>> > >> On Wed, Feb 24, 2021 at 3:57 PM Vladimir Sitnikov
>> > >> wrote:
>> > >>>
>> > >>> Thanks for pushing this forward.
>> > >>>
>> > >>> Would you please add search/sarg shrinking to RexShrinker?
>> > >>>
>> > >>> There are failures though:
>> > >>>
>> > >>> @Test void singleFuzzyTest() {
>> > >>>Random r = new Random();
>> > >>>r.setSeed(6321443803263498676L);
>> > >>>RexFuzzer fuzzer = new RexFuzzer(rexBuilder, typeFactory);
>> > >>>generateRexAndCheckTrueFalse(fuzzer, r);
>> > >>> }
>> > >>>
>> > >>> yields
>> > >>>
>> > >>> $node isAlwaysTrue, so it should simplify to TRUE unknownAsFalse
>> > >>>
>> > >>> SEARCH(-(COALESCE(?0.int0, CASE(=(CASE(false,
>> > >>
Fwd: [NOTICE] Git web site publishing to be done via .asf.yaml only as of July 1st
It seems like Calcite is affected by this change. I believe all that is necessary is to add .asf.yml to the calcite-site repository with the following contents: publish: whoami: master We have plenty of time to make the change, so if there are no objections or concerns, I'll commit this in the next week or two. -- Michael Mior mm...@apache.org -- Forwarded message - De : Daniel Gruno Date: lun. 31 mai 2021 à 09:41 Subject: [NOTICE] Git web site publishing to be done via .asf.yaml only as of July 1st To: Users TL;DR: if your project web site is kept in subversion, disregard this email please. If your project web site is using git, and you have not deployed it via .asf.yaml, you MUST switch before July 1st or risk your web site goes stale. Dear Apache projects, In order to simplify our web site publishing services and improve self-serve for projects and stability of deployments, we will be turning off the old 'gitwcsub' method of publishing git web sites. As of this moment, this involves 120 web sites. All web sites should switch to our self-serve method of publishing via the .asf.yaml meta-file. We aim to turn off gitwcsub around July 1st. ## How to publish via .asf.yaml: Publishing via .asf.yaml is described at: https://s.apache.org/asfyamlpublishing You can also see an example .asf.yaml with publishing and staging profiles for our own infra web site at: https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml In short, one puts a file called .asf.yaml into the branch that needs to be published as the project's web site, with the following two-line content, in this case assuming the published branch is 'asf-site': publish: whoami: asf-site It is important to note that the .asf.yaml file MUST be present at the root of the file system in the branch you wish to publish. The 'whoami' parameter acts as a guard, ensure that only the intended branch is used for publishing. ## Is my project affected by this? The quickest way to check if you need to switch to a .asf.yaml approach is to check out site source page at https://infra-reports.apache.org/site-source/ - if your site is listed in yellow, you will need to switch. This page will also tell you which branch you are currently publishing as your web site. This is (should be) the branch that you must add a .asf.yaml meta file to. The web site source list updates every hour. If your project site appears in green, you are already using .asf.yaml for publishing and do not need to make any changes. ## What happens if we miss the deadline? If you miss the deadline, don't fret. Your site will of course still remain online as is, but new updates will not appear till you create/edit the .asf.yaml and set up publishing. ## Who do we contact if we have questions? Please contact us at us...@infra.apache.org if you have any additional questions. With regards, Daniel on behalf of ASF Infra.
[jira] [Created] (CALCITE-4627) GPG signing failed when preparing Calcite release
Stamatis Zampetakis created CALCITE-4627:
Summary: GPG signing failed when preparing Calcite release
Key: CALCITE-4627
URL: https://issues.apache.org/jira/browse/CALCITE-4627
Project: Calcite
Issue Type: Bug
Affects Versions: 1.26.0
Reporter: Stamatis Zampetakis
While trying to prepare the release candidate the following error comes up from
time to time.
{noformat}
gpg: signing failed: Cannot allocate memory{noformat}
The result is that the task fails quite often. The full result output is shown
below.
{noformat}
./gradlew clean prepareVote -Prc=0
> Configure project :
Building Apache Calcite 1.27.0
> Task :initializeNexusStagingRepository
Initialized stagingRepositoryId orgapachecalcite-1622470091753 for repository
nexus
> Task :release:distTar
Source distribution is created:
/home/stamatis/Projects/Apache/calcite/release/build/distributions/apache-calcite-1.27.0-src.tar.gz
> Task :druid:signDruidPublication FAILED
gpg: signing failed: Cannot allocate memory
gpg: signing failed: Cannot allocate memory
> Task :mongodb:signMongodbPublication FAILED
gpg: signing failed: Cannot allocate memory
gpg: signing failed: Cannot allocate memory
> Task :core:signCorePublication FAILED
gpg: signing failed: Cannot allocate memory
gpg: signing failed: Cannot allocate memory
> Task :babel:signBabelPublication FAILED
gpg: signing failed: Cannot allocate memory
gpg: signing failed: Cannot allocate memory
Build calcite FAILURE reason:
org.gradle.execution.MultipleBuildFailures: Build completed with 4 failures.
at
org.gradle.initialization.DefaultGradleLauncher.runWork(DefaultGradleLauncher.java:262)
at
org.gradle.initialization.DefaultGradleLauncher.doClassicBuildStages(DefaultGradleLauncher.java:172)
at
org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:148)
at
org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:124)
Execution failed for task ':druid:signDruidPublication':
org.gradle.process.internal.ExecException: Process 'command 'gpg''
finished with non-zero exit value 2
at
org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:414)
at
org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)
at
org.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:175)
at
org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1166)
at
org.gradle.security.internal.gnupg.GnupgSignatory.sign(GnupgSignatory.java:69)
at
org.gradle.plugins.signing.type.AbstractSignatureType.sign(AbstractSignatureType.java:49)
at
org.gradle.plugins.signing.type.pgp.ArmoredSignatureType.sign(ArmoredSignatureType.java:40)
at
org.gradle.plugins.signing.type.AbstractSignatureType.sign(AbstractSignatureType.java:40)
at
org.gradle.plugins.signing.Signature.generate(Signature.java:440)
at org.gradle.plugins.signing.Sign.generate(Sign.java:206)
at
org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
at
org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
at
org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
at
org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
at
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:494)
at
org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
at
org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
at
org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
at
org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
at
org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
at
org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
at
org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
at
org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:71)
at
