Hi, we had numerous regressions in two last builds, I've opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=559352 https://bugs.eclipse.org/bugs/show_bug.cgi?id=559353 https://bugs.eclipse.org/bugs/show_bug.cgi?id=559355 And I guess there are more, we just don't see them because our test coverage is not the best. I don't know why should we continue this practice of blind "mass changes" for no good reason, that caused so many regressions so far. My best example of such regression, on which I've spent a full work week of my time, was https://bugs.eclipse.org/bugs/show_bug.cgi?id=551147. I'm tired to spend my time to do house keeping for others, and I don't see anyone else doing this work. I don't think this is fair. I would propose that committers that merge "mass changes" *must* do the work I do: 1) Check SDK build results after integration of mass changes and identify new failures 2) Report bugs for new failures 3) Identify offending commits and notify authors If this sounds as too much work, I would propose to re-think the "benefit" of mass changes. If we continue in the same way as today, at some point in time the code is "fully optimized" but Eclipse is not usable anymore. Kind regards, Andrey Loskutov Спасение утопающих - дело рук самих утопающих https://www.eclipse.org/user/aloskutov _______________________________________________ platform-dev mailing list platform-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
