As part of this, I'm going to: 1) Update configure.ac and CMakeLists to point to 1.0.0 version. Note that if someone is building off master, this might be a little weird because up until this change their builds would've 0.29.0 version and after this change it would be 1.0.0. But I guess it's unavoidable.
2) Transition the issues with Fix Version "0.29.0" to "1.0.0". I will make sure to turn off JIRA notification emails for this change to avoid spamming issues@. Thanks, On Wed, May 25, 2016 at 8:52 AM, Vinod Kone <vinodk...@apache.org> 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, >
