Document release process. #293
Conversation
Basically I suggest focusing this down to whatever we will need for a very limited 0.1. |
|
|
||
| Create a zfs pool. The following create a pool as a file in ``/``:: | ||
|
|
||
| truncate -s 2G /flocker-pool |
There was a problem hiding this comment.
This needs a better location. It should probably match what the vagrant image does.
| 4. Make sure all the tests pass on buildbot. | ||
| Go to the `buildbot <http://build.clusterhq.com/boxes-flocker>`_ and force a build on the just create branch. | ||
| XXX: buildbot needs to not merge forward on release branches | ||
| 5. Do the acceptance tests. (https://github.com/ClusterHQ/flocker/issues/315) |
There was a problem hiding this comment.
I would really like these to be automated, rather than manual, but we may not have time for that...
There was a problem hiding this comment.
Even if it is automated, it probably won't be run by buildbot in time for 0.1, so this would just be run those tests, in that case.
…ng a required spec file.
|
Ok. Sorry for my slow progress on this. But I think I've now been through the process from start to finish and addressed all the earlier (and my own) code review comments. I think it's good enough to do the first release. So I recommend that we merge it. If there are any missing or incorrect steps we can address those at the time of the release. |
|
The installation documentation in this branch refers to Also worth adding a link and a sentence to these new installation instructions in the (also new) flocker tutorial/requirements step. The tutorial doesn't currently explain how to install flocker-cli. |
| If you're interested in developing Flocker (as opposed to simply using it) see :doc:`contributing`. | ||
| Installing flocker-node | ||
| ======================= | ||
| .. note:: If you're interested in developing Flocker (as opposed to simply using it) see :doc:`contributing`. |
There was a problem hiding this comment.
Move this note above the headline, to previous section.
|
|
|
At this point I think we've spent way too much time with this branch open. Address remaining comments and then merge, and we can do additional cleanups as a second pass as we improve documentation separately (e.g. #87) or find issues when we do the test release. |
|
Ok. I addressed those final comments. Merging. |
Document the flocker release process Author: @tomprince Reviewers: @wallrj, @itamarst Fixes #292
Release documentation improvements resulting from the 0.0.6 practice release Author: @wallrj Reviewer: @adamtheturtle Refs #293
Fixes #292.
This is mostly an initial sketch for discussion.
This also at least partially addresses #86, #87, #126, #277.