Does this mean the work to deprecate the docker containerizer will be post-1.0, or have those plans changed?
On Wednesday, May 25, 2016, Vinod Kone <[email protected]> wrote: > Hi folks, > > As discussed in the previous community sync, we plan to cut a release > candidate for our next release (1.0) early next week. > > 1.0 is mainly centered around new APIs for Mesos. Please take a look at > MESOS-338 <https://issues.apache.org/jira/browse/MESOS-338> for blocking > issues. We got some great design and testing feedback for the v1 scheduler > and executor APIs. Please do the same for the in-progress v1 operator API > <https://docs.google.com/document/d/1XfgF4jDXZDVIEWQPx6Y4glgeTTswAAxw6j8dPDAtoeI/edit?pref=2&pli=1#> > . > > Since this is a 1.0, we would like to do the release a little differently. > > First, the voting period for vetting the release candidate would be a few > weeks (2-3 weeks) instead of the typical 3 days. > > Second, we are wiling to make major changes (scalability fixes, API fixes) > if there are any issues reported by the community. > > We are doing these because we really want the community to thoroughly test > the 1.0 release and give feedback. > > Thanks, > -- Text by Jeff, typos by iPhone
