The vote received enough votes for a resolution. I will prepare a
result shortly.
I have created issues to improve the release process:
IGNITE-15860 [Extensions] Automated RC preparation and testing at
Apache TeamCity [1]
IGNITE-15861 [Extensions] Move examples to separate maven projects [2]
+1 (binding)
> 1 нояб. 2021 г., в 17:41, Denis Magda написал(а):
>
> +1 (binding)
>
> Support to release the integration and then bring in essential automation
> for testing.
>
> -
> Denis
>
>
> On Wed, Oct 27, 2021 at 4:48 AM Nikita Amelchev
> wrote:
>
>> Dear Ignite Community,
>>
>> I
+1 (binding)
Support to release the integration and then bring in essential automation
for testing.
-
Denis
On Wed, Oct 27, 2021 at 4:48 AM Nikita Amelchev
wrote:
> Dear Ignite Community,
>
> I have uploaded a release candidate of extensions modules:
> - spring-tx-ext 1.0.0
> -
Ilya, thank you for your comments.
The documentation has been updated according to your suggestions - [1].
The Spring Cache and Spring Transactions integrations have now been
restricted to use with Ignite only since version 2.11 (the spring-tx and
spring-cache integration classes were migrated
Hello!
I think we should write in documentation that the module is only suitable
for AI 2.13 or later.
And then in AI 2.13 we remove these classes from ignite-spring.
It does not make sense to use this module before AI 2.13. It may be
possible but does not have any practical purpose.
Regards,
Hi Igniters, PMCs,
Remind you that according to ASF policy [1] for a release vote to
pass, a minimum of three positive votes (full binding +1, not
fractions) and more positive than negative votes must be cast.
I suggest continuing the vote until there are enough votes for a
resolution. The
Ilya, for Ignite 2.10 versions and earlier spring-tx and spring-cache
integrations are stored in the ignite-spring module. Initially, there
were no dedicated modules for them. As I see, we cannot fully migrate
the ignite-spring module as it is responsible for parsing Ignite XML
configurations
Hello!
+ 0.5
> Apache Ignite 2.10.0 and earlier the ignite-spring-cache-ext dependency
must be added to classpath before ignite-spring, due to duplication of
Spring Cache integration classes.
I think this recommendation does not have much sense - the order of
classpath and maven dependency
+1
I think we should prepare the lists of todos/jira issues to automate
the release cycle.
On Wed, 27 Oct 2021 at 14:13, Ivan Daschinsky wrote:
>
> +0.5 from me
>
> 1. Checked signatures and sha512 sums -- both OK
> 2. Both source packages compiles and tests passed -- OK
> 3. Manually created
+0.5 from me
1. Checked signatures and sha512 sums -- both OK
2. Both source packages compiles and tests passed -- OK
3. Manually created examples project from provided examples in
spring-tx-ext -- works OK with spring 5.3.11 (with manual exclusion of
spring dependencies) - OK
4. Checked previous
My -0 here, since the is no automated RC preparation and testing at Apache
TeamCity again.
Next time, I will vote with -1 if a new vote is not covered by public
automated preparation/testing as the AI release does.
On Wed, Oct 27, 2021 at 11:48 AM Nikita Amelchev
wrote:
> Dear Ignite Community,
11 matches
Mail list logo
