> My proposal is not about creating a separate repository for the spring-data
extension - just left a single module
Yeah, you're correct. I mean that we need a single point of truth for
spring-data - single repository or single module. I'm +1 here.
> So creating some branches to store obsolete co
Maksim,
Currently, we have a single repository where all extensions are stored
as separate modules - [1]
My proposal is not about creating a separate repository for the
spring-data extension - just left a single module for the spring-data
extension and proceed with its developments the same wa
Hi Mikhail,
> remove extension modules that are tied to the specific Spring Data versions
- keep only a single spring-data-ext module. For now, it will contain code
for the latest Ignite Spring Data integration - ignite-spring-data-2.2-ext.
I'm +1 for having a single repository for the spring-dat
Thank you it will very help us
> Hello Stephen,
>
> I'm planning to release the extensions soon. Tests are OK, however,
> some TC Suites still need to be configured.
>
> On Wed, 26 Jan 2022 at 21:07, Stephen Darlington
> wrote:
> >
> > Do we know what happened with this thread? I just saw a quest
