Looks we did a release for the docs with the tools release. Is it possible to 
name it 6.x instead of 6.0.0? All URLs to 6.0.0 will break if we do that but we 
should do that sooner rather than later to minimize impact.

As discussed, micro-versioning of docs does not buy us much. I'll enhance our 
cordova-docs readme and editorial guide for docs with details on how we handle 
versioning.

-Nikhil

-----Original Message-----
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Thursday, January 21, 2016 2:50 PM
To: dev@cordova.apache.org
Subject: Re: Docs versioning scheme

SGTM! +1


@purplecabbage
https://na01.safelinks.protection.outlook.com/?url=risingj.com&data=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=fiC5HqwZWlaOSZD4ipn97isk7hjFjVCht9IzgKZKnFA%3d

On Thu, Jan 21, 2016 at 1:47 PM, Steven Gill <stevengil...@gmail.com> wrote:

> +1
>
> On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal 
> <nikhi...@microsoft.com
> >
> wrote:
>
> > Should we version our docs on every major version (instead of minor
> > version) of cordova CLI that comes out? Should the next version of 
> > the
> docs
> > be "6.x"? Honestly, not much changes every minor release and 
> > maintaining multiple copies has quite a few downsides w.r.t. SEO 
> > (referring to older versions of docs), slow docs builds, huge website 
> > duplication.
> >
> > Lot of our docs relate to platform updates and we need clear 
> > sections within them that specify the version of the platform for 
> > which the docs apply to. For example, Android 5.1 will introduce new 
> > lifetime concepts which will be part of Cordova 6.0 docs release. 
> > It's best for the text of the docs itself to have something along 
> > the lines of "This applies to cordova-android > 5.1"
> >
> > Similarly, significant future updates to CLI/Lib features can 
> > contain the same "This applies to cordova > 6.2".
> >
> > I think it will lead to a simpler model on our website and prevent 
> > future version explosion [1].
> >
> > Thanks,
> > Nikhil
> >
> > [1] 
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fimgu
> > r.com%2fvkeNvUL&data=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846
> > b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=
> > Yh%2b9h4MUN9VfUADA1unTmUExqioMs75xG1HjVYmDSBc%3d
> >
> >
>

Reply via email to