[infinispan-dev] Granularity of cache store Git repositories

[Mircea Markus]

On 14 Aug 2013, at 19:12, Galder Zamarreño <galder at redhat.com> wrote:

>> 
>> On 14 Aug 2013, at 08:09, Galder Zamarreño <galder at redhat.com> wrote:
>> 
>>> IMO, the separate repository per cache store would make sense if each cache store was maintained by a separate person, and this person would make sure that it's kept up to date, he/she releases it, they have their community or members who contribute to that cache store…etc. I don't think we're there yet though.
>> 
>> Isn't that the goal, though?  To have these maintained separately, at their own pace?
> 
> ^ Sure, but what happens when we change something in core/ and you need to update all existing cache stores.

That should only happen for major releases, otherwise custom stores would break as well. Unless it's a new test you're adding that should be inherited by all stores, but that is rather rare. 

> Are we gonna go after each cache store and make the corresponding changes? (as I said earlier, that'd be 9 pull reqs…),
> or are we leaving it to whoever maintains them to deal with these changes?

For major changes, the stores should be upgraded one by one, by their maintainer. 
Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)