> On April 24, 2015, 8:17 a.m., Alexander Rukletsov wrote: > > LGTM (not a native speaker). Shouldn't we commit this RR after introducing > > master endpoints : )?
> Shouldn't we commit this RR after introducing master endpoints : )? Updated the description to make this clear. > On April 24, 2015, 8:17 a.m., Alexander Rukletsov wrote: > > docs/reservation.md, lines 97-100 > > <https://reviews.apache.org/r/32982/diff/1/?file=921006#file921006line97> > > > > Do you want to mention HTTP response codes for response? Yes. Thanks for pointing that out. My plan is to punt the decision to the implementation of master API endpoints. - Michael ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/32982/#review81459 ----------------------------------------------------------- On May 8, 2015, 6:57 p.m., Michael Park wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/32982/ > ----------------------------------------------------------- > > (Updated May 8, 2015, 6:57 p.m.) > > > Review request for mesos, Alexander Rukletsov and Timothy Chen. > > > Bugs: MESOS-2205 > https://issues.apache.org/jira/browse/MESOS-2205 > > > Repository: mesos > > > Description > ------- > > See summary. > > NOTE: Do not commit until master API endpoints are implemented for dynamic > reservations. > > > Diffs > ----- > > docs/reservation.md PRE-CREATION > > Diff: https://reviews.apache.org/r/32982/diff/ > > > Testing > ------- > > Documentation. > > > Thanks, > > Michael Park > >
