cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From simonfiddaman <>
Subject [GitHub] cloudstack-docs-rn pull request: Update CS RelNotes 4.2.x to 4.3
Date Wed, 16 Apr 2014 14:10:29 GMT
GitHub user simonfiddaman opened a pull request:

    Update CS RelNotes 4.2.x to 4.3

     - Break out validation step as it applies to all upgrades and installations
     - Update visual format of commands
     - Update instructions for 4.2.x upgrade
     - Reordered and clarified agent upgrade steps

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #6
commit 617b141e18e686af6af431e586d761e5566f6097
Author: Simon Fiddaman <>
Date:   2014-03-25T15:37:00Z

    Update format of 4.2.0 upgrade commands
    Make Ubuntu and CentOS commands consistently formatted ( $ sudo ... ) for 4.2.0 upgrade

commit 8a2d3f8ee038251d3b53fed3d287a81fcdbc189c
Author: Simon Fiddaman <>
Date:   2014-03-25T16:12:31Z

    Update 4.2.0 upgrade instructions
    Update 4.2.0 upgrade instructions for Ubuntu and CentOS to correct apt / yum usage.

commit 113541ee5c507cde950cbe979fa38e1d3828bc4e
Author: Simon Fiddaman <>
Date:   2014-03-26T08:06:32Z

    Update references to 4.2.0
    Update references to version 4.2.0 to version 4.2.x. 
    Update references to versioned repository 4.2.0 to 4.2 (as the repository should be specific
to the 4.2 release, not the point-release).

commit 6b9fad09ef75ebde6ffdecb4a41ae13384a83957
Author: Simon Fiddaman <>
Date:   2014-03-26T08:25:09Z

    Move source tarball verification up document
    The source tarball verification steps can and should be performed independently of the
specific 4.2.x to 4.3.0 upgrade steps. Move the source tarball verification steps to the beginning
of the document to simplify the 4.2.x upgrade steps and minimise downtime (should these steps
be performed in sequence as described).


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message