If we did feature based releases, we could hold the release for the
documentation.
Since we do time based releases, it so happened that the release went
through before we could get the docs done.

I'll be working on the docs shortly :-)

—
*Joris Van Remoortere*
Mesosphere

On Thu, Feb 4, 2016 at 8:59 AM, Kapil Arya <ka...@mesosphere.io> wrote:

> That's a good point, Niklas!
>
> IMO, we should be able to ship a major feature as long as we have an
> assurance that the user doc will land in the next few days (not
> weeks).
>
> On Thu, Feb 4, 2016 at 11:55 AM, Niklas Nielsen <n...@qni.dk> wrote:
> > Thanks Jie and Kapil! Looking forward to it.
> >
> > I did read the proposal, but playing the devils advocate for a bit; how
> can
> > we ship a 'major feature' without bundled user documentation? Referring
> to
> > tickets and design docs (which may/or may not be the way things ended up
> > getting implemented) or to code is not good enough, in my mind.
> >
> > Should we line up some expectations to available user docs, example
> > framework code, etc. before announcing the availability of a feature?
> >
> > Niklas
> >
> > On Thu, Feb 4, 2016 at 5:41 PM, Kapil Arya <ka...@mesosphere.io> wrote:
> >>
> >> And here is the ticket tracking the user doc:
> >> https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
> >> blog post once the doc is ready :-).
> >>
> >> On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu <yujie....@gmail.com> wrote:
> >> > Niklas,
> >> >
> >> > I think Joris is still working on the user doc for multi-disk support
> in
> >> > Mesos.
> >> >
> >> > - Jie
> >> >
> >> > On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen <n...@qni.dk> wrote:
> >> >
> >> >> Awesome guys!
> >> >>
> >> >> Kapil, we usually linked to the user documentation in the blog to the
> >> >> new
> >> >> features. Do you have a link to the docs on multiple disk resources?
> >> >>
> >> >> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya <ka...@mesosphere.io>
> >> >> wrote:
> >> >>
> >> >> > And here is the blog post:
> >> >> > http://mesos.apache.org/blog/mesos-0-27-0-released.
> >> >> >
> >> >> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park <mp...@apache.org>
> >> >> > wrote:
> >> >> > > Kapil is currently working on it. We'll publish it shortly :)
> >> >> > >
> >> >> > > On 3 February 2016 at 13:41, Benjamin Mahler <bmah...@apache.org
> >
> >> >> wrote:
> >> >> > >>
> >> >> > >> Great! Is a blog post on the way?
> >> >> > >>
> >> >> > >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park <mp...@apache.org
> >
> >> >> wrote:
> >> >> > >>
> >> >> > >> > Hi all,
> >> >> > >> >
> >> >> > >> > The vote for Mesos 0.27.0 (rc2) has passed with the
> >> >> > >> > following votes.
> >> >> > >> >
> >> >> > >> > +1 (Binding)
> >> >> > >> > ------------------------------
> >> >> > >> > Vinod Kone
> >> >> > >> > Joris Van Remoortere
> >> >> > >> > Till Toenshoff
> >> >> > >> >
> >> >> > >> > +1 (Non-binding)
> >> >> > >> > ------------------------------
> >> >> > >> > Jörg Schad
> >> >> > >> > Marco Massenzio
> >> >> > >> > Greg Mann
> >> >> > >> >
> >> >> > >> > There were no 0 or -1 votes.
> >> >> > >> >
> >> >> > >> > Please find the release at:
> >> >> > >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
> >> >> > >> >
> >> >> > >> > It is recommended to use a mirror to download the release:
> >> >> > >> > http://www.apache.org/dyn/closer.cgi
> >> >> > >> >
> >> >> > >> > The CHANGELOG for the release is available at:
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >
> >> >> >
> >> >>
> >> >>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
> >> >> > >> >
> >> >> > >> > The mesos-0.27.0.jar has been released to:
> >> >> > >> > https://repository.apache.org
> >> >> > >> >
> >> >> > >> > The website (http://mesos.apache.org) will be updated
> shortly to
> >> >> > reflect
> >> >> > >> > this release.
> >> >> > >> >
> >> >> > >> > Thanks,
> >> >> > >> >
> >> >> > >> > Tim, Kapil, MPark
> >> >> > >> >
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Niklas
> >> >>
> >
> >
> >
> >
> > --
> > Niklas
>

Reply via email to