[
https://issues.apache.org/jira/browse/CB-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Gill resolved CB-7226.
----------------------------
Resolution: Fixed
> Update Documentation for Independent releases
> ---------------------------------------------
>
> Key: CB-7226
> URL: https://issues.apache.org/jira/browse/CB-7226
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: Docs
> Reporter: Steve Gill
>
> Cordova-docs:
> - Most of the docs are not actually affected by platform versions.
> - Mainly though, it's the platform guides that are.
> - Two options:
> Option 1
> Set default version to "edge" & always annotate with "added in X.X.X, removed
> in X.X.X"
> No more cutting versions. Update docs.cordova.io when changes occur or some
> other interval.
> Option 2
> - Docs get same version as CLI & get tagged alongside cli releases
> - We can still annotate with "added in X.X.X, removed in X.X.X" where it
> makes sense. (like the upgrade guides)
> - Point docs.cordova.io to edge
> - Dropdown will show tagged versions
> Pros:
> - Keeps a public history of older docs at a point in time. Easy to use for
> people who don't want the latest
> - Gives us flexibility in changing docs and not worrying about older
> versions.
> Earlier proposal can be found at
> https://docs.google.com/document/d/1qwpypH7sH0wH9Sbesmg8JZow-l8IqdZtF1BtLUZb1As/edit.
> Will need to be updated
> p.s. regardless of option that is picked, guides should eventually live in
> platform repos and be linked from docs (or docs generate pulls from them from
> platform repos at build time).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
