That sounds good. We can have the "latest" (not yet released) version. But having a view that is tied to a particular release will ensure what is documented is what they are using.
On Wed, May 17, 2017 at 10:51 AM, Chiyuan Zhang <plus...@gmail.com> wrote: > We can provide versioned docs. AFAIK Sphinx support docs of different > versions (see e.g. the top left corner for switch between versions of docs > for Python here: https://docs.python.org/2/library/index.html ). So we can > have a "latest" doc and a few history versioned doc that is to be built > whenever we make a new release. > > - chiyuan > > On Wed, May 17, 2017 at 1:47 PM, Naveen Swamy <mnnav...@gmail.com> wrote: > > > If we have a regular and frequent release cadence, then building > mxnet.io > > would be good. > > Since our releases are not that frequent, I am not very inclined to wait > > for a release candidate to get new tutorials/howtos onto the website. > that > > being said we can restrict to build tutorials/howtos/other sections., > from > > tip of the master and API documentation to come from a release tag. > > > > -Naveen > > > > > > > > On Wed, May 17, 2017 at 10:05 AM, Madan Jampani <madan.jamp...@gmail.com > > > > wrote: > > > > > We are currently building mxnet.io directly from HEAD of master. > > > With the next release we should make sure mxnet.io is built from a > > release > > > tag. This will ensure the docs website reflects the latest stable > > release. > > > > > > Any one disagrees? > > > > > > Madan. > > > > > >
