Igniters,
It seems that we came to decision on change of Ignite dependency scopes
to "provided". Don't we?
The corresponding ticket [1] is ready to final review. Saikat Maitra
have already reviewed and approved PR [2].
Could some committer take a final look?
[1] - https://issues.apache.org/jira/browse/IGNITE-13634
[2] - https://github.com/apache/ignite-extensions/pull/28
On 28.10.2020 20:24, Saikat Maitra wrote:
Hi
Alex,
Yes, we can start releasing the extensions modules. I would like to also
help in releasing a few extensions, it will also help me to be familiarized
with the release process.
Mikhail and I have been having discussion about whether we should use
provided scope for dependencies or shall we use 2.9.0 for ignite.version
for the extensions modules?
Jira : https://issues.apache.org/jira/browse/IGNITE-13621
PR : https://github.com/apache/ignite-extensions/pull/28/files
Please let us know your thoughts.
Denis,
We have the following jira ticket for documentation work for ignite
extensions releases.
https://issues.apache.org/jira/browse/IGNITE-12951
Please let us know if the scope in the issue looks good.
Regards,
Saikat
On Wed, Oct 28, 2020 at 10:28 AM Denis Magda <dma...@apache.org> wrote:
Alex,
Should we create a dedicated ticket for the documentation changes or can we
reuse IGNITE-13634? As a bare minimum, we need to update maven artifacts'
names and versions:
https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
-
Denis
On Wed, Oct 28, 2020 at 5:10 AM Alexey Goncharuk <
alexey.goncha...@gmail.com>
wrote:
Igniters,
Since Ignite 2.9 has been released, I think we can now release the
extension modules related to streaming.
I noticed that unlike spring autoconfigure, the streamer extensions
dependencies do not have provided scope, so I created a ticket to fix
that
[1]. Anything else we should fix before releasing the extensions?
[1] https://issues.apache.org/jira/browse/IGNITE-13634
--AG
