I was hoping we could resolve most if not all the bugs marked as
[regression] before rolling 0.2.0:
https://launchpad.net/mir/+milestone/0.2.0
Two of them were known at the time of releasing 0.1.9 and I personally
think we should wait until most of the regressions have fixes landed.
Most of
This is close to what happens in a general sense.
I would say we're closer to a 2 to 3 week cycle (dependent on getting a
silo, ci-train process etc)
wrt API/ABI breaks, I do believe things will get better, but so far, the
ABI churn has not been predictable enough.
Also, keep in mind...there is a
In general, I wonder if the following makes sense :
- if the new content is causing ABI/API breaks, we should promote pretty
soon after it's in devel. Hopefully, that won't happen so often. If/when it
does, we don't want to sit on it for long.
o To minimize breaks (and releases), if we are
Yeah at least 1) should be in there.
On Tue, May 13, 2014 at 5:16 PM, Kevin Gunn wrote:
> hi all,
> Just a poll for feedback.
> Its been a while since our 0.1.9, and since we keep devel up to snuff for
> promotion to trunk we could pull at any time. Some might feel like we
> should promote now.
hi all,
Just a poll for feedback.
Its been a while since our 0.1.9, and since we keep devel up to snuff for
promotion to trunk we could pull at any time. Some might feel like we
should promote now. But I feel the next promotion should probably wait for
the following to land on devel:
1) the improve
