Just to be sure. This is branch is not ready for prime time yet (not thoroughly tested). There are at least 2 outstanding bugs (MESOS-481<https://issues.apache.org/jira/browse/MESOS-481> , MESOS-482 <https://issues.apache.org/jira/browse/MESOS-482>) that we are aware of. Having said that, if you do take it for a spin, do let us know :)
On Thu, May 30, 2013 at 11:52 AM, Brenden Matthews < [email protected]> wrote: > Great! Going to try it out. I'm really excited about this feature. > > > On Thu, May 30, 2013 at 11:35 AM, Vinod Kone <[email protected]> wrote: > > > This is now done. > > > > Updated Branches: > > refs/heads/0.13.x [created] cc5e1e7b7 > > > > > > On Wed, May 29, 2013 at 9:39 AM, Brenden Matthews < > > [email protected]> wrote: > > > > > Sounds good! I'd probably target 0.14.x for my Hadoop changes rather > > than > > > 0.13.x. > > > > > > > > > On Tue, May 28, 2013 at 2:00 PM, Vinod Kone <[email protected]> > wrote: > > > > > > > Hi folks, > > > > > > > > We are planning to release a new feature (called "Slave Restart") > that > > > > allows organizations to upgrade mesos without disrupting the running > > > tasks. > > > > Previously, when the slave process was stopped for an upgrade, the > > tasks > > > > running on that slave committed suicide. With the new feature, the > > tasks > > > > can keep running and connect back to the upgraded slave, when it > > > restarts. > > > > > > > > Since this feature includes a huge amount of code change, we would > like > > > to > > > > create a new branch (0.13.x). The new branch helps us to commit bug > > fixes > > > > easily, test the feature and also unblocks people from committing > other > > > > major changes/features to master/trunk. We have been testing "Slave > > > > Restart" feature for a while, but need some more time to iron out > some > > > > kinks. Note that, any bug fixes that relate to "Slave Restart" will > go > > to > > > > both "master" and "0.13.x". > > > > > > > > Let us know if you have any questions/concerns. > > > > > > > > > >
