On 30/09/14 02:42, Daniel van Vugt wrote:
> Noting that the hiding of headers in Mir 0.8, while causing some
> teething problems, has been very successful in reducing ABI bumps.
> Although we did bump ABIs in 0.8 it wasn't until late in the cycle
> that changes were committed needing any bumps. So
Noting that the hiding of headers in Mir 0.8, while causing some
teething problems, has been very successful in reducing ABI bumps.
Although we did bump ABIs in 0.8 it wasn't until late in the cycle that
changes were committed needing any bumps. So that's a great improvement.
I do like the ide
To me, at this point, when to expose is more important than what to expose.
What we have now (Don't expose something unless it's used externally, but
have it ready in a staging/playground area) makes sense for efficiency
which is where the emphasis should be at this point. In time, we migrate
APIs,
This is good to think about, because it'll help us sort out the headers and
make sure that core concepts of mir are available to our users. It'll also
let us refocus; that is, make sure that the interfaces we want the
downstreams to use match up with the needs of the downstreams.
I think the compo
