Gotcha. So if I found a regression in 5.11.x I imagine the best way to make sure it’s address is to submit a merge request with a unit test that exposes the issue?
I’m going to be stuck on 5.10.2 until this is fixed :-P On Thu, Feb 26, 2015 at 4:27 PM, Tim Bain <[email protected]> wrote: > My impression as an outside observer is that the plan is always to > not maintain the versions after release of a x.x.0 version if we can get > away with it, and that incidental releases are always unplanned due to > issues found after release of the x.x.0 release that are deemed severe > enough to not wait for the next minor/major version release. So if those > observations are right, it's not possible to predict whether the 5.10.x > branch will be released until major issues are found (or not). > > But the people who actually manage the releases might have more detailed > insight than my guesses... > > On Thu, Feb 26, 2015 at 4:50 PM, Kevin Burton <[email protected]> wrote: > > > Just curious as I found a regression on advisories in 5.11. > > > > If 5.10 is still going to be maintained I need to fix my branches to work > > with 5.10 because our app breaks on 5.11. > > > > Kevin > > > > -- > > > > Founder/CEO Spinn3r.com > > Location: *San Francisco, CA* > > blog: http://burtonator.wordpress.com > > … or check out my Google+ profile > > <https://plus.google.com/102718274791889610666/posts> > > <http://spinn3r.com> > > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
