[
https://issues.apache.org/jira/browse/MESOS-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180593#comment-15180593
]
Vinod Kone commented on MESOS-4859:
-----------------------------------
I fixed some of it when doing the 0.28.0 release.
But the bigger thing I realized was that people people were describing API
changes etc in upgrades.md and CHANGELOG, sometimes inconsistently. I think it
would be great if we can cleanup upgrades.md to keep it specific to upgrade
instructions (for e.g., compatiblity matrix that we talked about) and move all
the other stuff to CHANGELOG.
Thoughts?
> Add explicit upgrade instructions to the docs
> ---------------------------------------------
>
> Key: MESOS-4859
> URL: https://issues.apache.org/jira/browse/MESOS-4859
> Project: Mesos
> Issue Type: Improvement
> Components: documentation
> Reporter: Greg Mann
> Labels: documentation, mesosphere
>
> The documentation currently contains per-version upgrade guidelines, which
> for recent releases only outlines the upgrade concerns for that version,
> without detailing explicit upgrade instructions.
> We should add explicit upgrade instructions to the top of the upgrades
> documentation, which can be supplemented by the per-version concerns.
> This is done within the upgrade docs for some early versions, with text like:
> {code}
> In order to upgrade a running cluster:
> Install the new master binaries and restart the masters.
> Upgrade the schedulers by linking the latest native library and mesos jar (if
> necessary).
> Restart the schedulers.
> Install the new slave binaries and restart the slaves.
> Upgrade the executors by linking the latest native library and mesos jar (if
> necessary).
> {code}
> Instructions to this effect should be featured prominently in the doc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
