mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Rukletsov <a...@mesosphere.com>
Subject Re: Version numbers in docs
Date Wed, 03 Feb 2016 12:38:35 GMT
But before we switch to version specific docs, I would like to keep the
version when a certain feature was introduced. This information should not
necessarily open the doc, but should be present somewhere, perhaps as a
side note.

On Wed, Feb 3, 2016 at 11:04 AM, Alexander Rojas <alexander@mesosphere.io>
wrote:

> I actually like the idea to have version specific documentation, since it
> is kind of the standard way of going about things.
>
> +1 to that.
>
>
> > On 03 Feb 2016, at 01:53, Neil Conway <neil.conway@gmail.com> wrote:
> >
> > I agree we should remove this text after some period of time has
> > passed since that version of Mesos was released; it is quite
> > distracting.
> >
> > The proper long-term fix is probably to have version-specific docs. So
> > all the documentation at
> >
> > /documentation/v0.27/...
> >
> > would implicitly discuss the features that are present in Mesos 0.27.
> > That would eliminate a lot of the need for version number references
> > in the documentation text itself.
> >
> > Neil
> >
> > On Tue, Feb 2, 2016 at 4:48 PM, Greg Mann <greg@mesosphere.io> wrote:
> >> Hi all!
> >> In our docs, you find such sentences as:
> >>
> >> "Mesos 0.15.0 added support for framework authentication, and 0.19.0
> added
> >> slave authentication."
> >>
> >> It's a minor point, but I wonder how long we should maintain such
> version
> >> numbers in the docs? In the example above, my feeling is that we are far
> >> enough past 0.19.0 that we could change this to read simply, "Mesos
> >> supports authentication of both frameworks and slaves".
> >>
> >> Thoughts?
> >>
> >> Cheers,
> >> Greg
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message