Browse code

add a breakathon for testing

Docker-DCO-1.1-Signed-off-by: Charlie Lewis <charliel@lab41.org> (github: cglewis)

Charlie Lewis authored on 2014/03/14 03:15:52
Showing 1 changed files
... ...
@@ -178,7 +178,23 @@ docker run \
178 178
        hack/release.sh
179 179
 ```
180 180
 
181
-### 9. Apply tag
181
+### 9. Breakathon
182
+
183
+Spend several days along with the community explicitly investing time and
184
+resources to try and break Docker in every possible way, documenting any
185
+findings pertinent to the release.  This time should be spent testing and
186
+finding ways in which the release might have caused various features or upgrade
187
+environments to have issues, not coding.  During this time, the release is in
188
+code freeze, and any additional code changes will be pushed out to the next
189
+release.
190
+
191
+It should include various levels of breaking Docker, beyond just using Docker
192
+by the book.
193
+
194
+Any issues found may still remain issues for this release, but they should be
195
+documented and give appropriate warnings.
196
+
197
+### 10. Apply tag
182 198
 
183 199
 ```bash
184 200
 git tag -a $VERSION -m $VERSION bump_$VERSION
... ...
@@ -188,12 +204,12 @@ git push origin $VERSION
188 188
 It's very important that we don't make the tag until after the official
189 189
 release is uploaded to get.docker.io!
190 190
 
191
-### 10. Go to github to merge the `bump_$VERSION` branch into release
191
+### 11. Go to github to merge the `bump_$VERSION` branch into release
192 192
 
193 193
 Don't forget to push that pretty blue button to delete the leftover
194 194
 branch afterwards!
195 195
 
196
-### 11. Update the docs branch
196
+### 12. Update the docs branch
197 197
 
198 198
 ```bash
199 199
 git checkout docs
... ...
@@ -207,7 +223,7 @@ Updating the docs branch will automatically update the documentation on the
207 207
 after the merge. The docs will appear on http://docs.docker.io/. For more
208 208
 information about documentation releases, see `docs/README.md`.
209 209
 
210
-### 12. Create a new pull request to merge release back into master
210
+### 13. Create a new pull request to merge release back into master
211 211
 
212 212
 ```bash
213 213
 git checkout master
... ...
@@ -225,7 +241,7 @@ echo "https://github.com/dotcloud/docker/compare/master...merge_release_$VERSION
225 225
 Again, get two maintainers to validate, then merge, then push that pretty
226 226
 blue button to delete your branch.
227 227
 
228
-### 13. Rejoice and Evangelize!
228
+### 14. Rejoice and Evangelize!
229 229
 
230 230
 Congratulations! You're done.
231 231