David - now that a week has passed, do you see any further reason to wait? We are still seeing minor cosmetic issues and bug fixes pop up. It would be > pretty harmful to have to deal with these for an entire release
It's worth stating the obvious - we can cut point releases when necessary to address this type of issue. On Mon, Oct 30, 2017 at 8:41 AM, David McLaughlin <dmclaugh...@apache.org> wrote: > I'd like another week of feedback to incorporate changes of the new UI. We > are still seeing minor cosmetic issues and bug fixes pop up. It would be > pretty harmful to have to deal with these for an entire release. > > On Mon, Oct 30, 2017 at 8:34 AM, Erb, Stephan <stephan....@blue-yonder.com > > > wrote: > > > Sounds good to me. Getting the release out quickly will allow us to > remove > > the old mybatis/h2 code sooner. > > > > I planned on upgrading to Mesos 1.4. Unfortunately this is currently > > blocked by a missing mesos.interface package on PyPI. I send a mail out > to > > the Mesos Dev list but I am still waiting for a response. So this will > have > > to wait for 0.20. > > > > On 29.10.17, 23:15, "Bill Farner" <wfar...@apache.org> wrote: > > > > Folks, > > > > I propose we cut our 0.19.0 release soon. We have built up a > > respectable > > set of unreleased changes > > <https://github.com/apache/aurora/blob/master/RELEASE-NOTES.md>. I > am > > happy to perform this release, and should be able to do so as soon as > > this > > week. > > > > Please chime in here if there is any outstanding work that should > > block a > > release. > > > > > > Cheers, > > > > Bill > > > > > > >
