>> But shouldn't build system *of a modular product* be designed such
>> that a wrong commit in module "m" does not affect anyone other than those
>> who depend on latest version of "m"?
>>
>> I understand we are not there yet, but that should be our goal.
> Yes, that's our goal, but the goal can't achieved by build team alone.
> Developers have to first modularize their components. Until then, we
> should have a monolithic build system to avoid all the build problems we
> are having today.
I agree. I had no intention to blame it on someone.
How should developers help?
Have we identified specific action items that module developers must finish?
Have we identified modules (and owners) that make v3 Prelude release?
I don't expect one person to know answers to all of these, but we need
to know these answers, isn't it?