[erlang-questions] modular otp concerns

[Michael Truog]

On 02/18/2014 09:30 AM, Björn-Egil Dahlberg wrote:
> If/when we split the OTP repository, and this split should be on the level where we have specific versions i.e. on application level. It has solve the issue of easy delivery of new patches and release on these specific applications. Some have voiced a concern that it will simply be to many repos and we should instead group them, i.e. Orber + cos* etc. I say fine, if so then those applications should have one version (and be a single application). One versioned entity per repository thank you. 
My main concern is: if the OTP repository is split, we still need the concept of a "version set", so a set of versions for all of OTP that are known to work together, just to help people avoid any potential for instability.  With that concept in place, it shouldn't be a problem either way, and you are probably aware of the issue, but I wanted to mention it due to the added complexity that not having a "version set" concept can cause.  If you don't have that concept, of versions grouped into a release, basically, then you run into a combinatorial problem during testing, which makes testing take longer (i.e., for all end-users).