Dear Community,
The release candidate is ready.
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc1/
The following staging can be used for testing:
Pavel, currently they offers only free 14-day trial, unfortunately
чт, 30 дек. 2021 г. в 13:16, Pavel Tupitsyn :
> Ivan,
>
> MyGet is free within some limits.
> It was introduced to make release verification easier - no need to unzip
> nuggets into a local dir, just install them from MyGet.
>
>
> it would be great to release a new SQL engine in 2.13 as an
experimental feature.
++1
On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov
wrote:
> Andrey,
>
> > Is this [1] a full scope of the tickets that MUST be resolved before the
> engine could be merged?
> Yes, we must resolve at least these
Ivan,
MyGet is free within some limits.
It was introduced to make release verification easier - no need to unzip
nuggets into a local dir, just install them from MyGet.
Nikita,
No, we won't upload NuGet packages to any registry before a successful RC
vote.
Only then we'll push them to nuget.org
Andrey,
> Is this [1] a full scope of the tickets that MUST be resolved before the
engine could be merged?
Yes, we must resolve at least these tickets before merging. If you see any
other release blockers fill free to attach them to this ticket.
> I think we have to add instructions to the
I'm sorry, but I've never understand the purpose of uploading to MyGet. It
is not free registry and it is required to pay to use it.
чт, 30 дек. 2021 г. в 12:34, Nikita Amelchev :
> Pavel, thank you.
>
> The "[3] Build & Upload Nuget Staging Packages" configuration also
> pushes packages to the
Pavel, thank you.
The "[3] Build & Upload Nuget Staging Packages" configuration also
pushes packages to the MyGet.
Will packages be published to some package registry?
чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn :
>
> NuGet packages are now prepared as part of the main config "[1] Release
>
Alex,
it would be great to release a new SQL engine in 2.13 as an
experimental feature.
Is this [1] a full scope of the tickets that MUST be resolved before the
engine could be merged?
I think we have to add instructions to the readme file on how to turn a new
SQL engine on.
Also, I don't like
Alex, great !
If someone wants to touch codebase somehow plz use this branch [1]
Test passed can be found here [2] [3]
[1] https://github.com/apache/ignite/tree/sql-calcite/modules/calcite
[2]
