@@ -189,7 +189,14 @@ have a heading added at the top for the *next* version.
189
189
- The ` ${PROJECT_NAME}_SUPPORTED_RELEASE ` variable should be ` ON ` for any
190
190
release branch, ` OFF ` for master.
191
191
192
- 5 . Make sure everything passes the usual CI workflow. Also check the daily or
192
+ 5 . In the https://github.com/OpenImageIO/oiio-images project, create a branch
193
+ ` RB-x.y ` for the major/minor branch, and in the main oiio repo, update
194
+ src/build-scripts/install_test_images.bash to specify ` -b RB-x.y ` in the
195
+ checkout of oiio-images to ensure CI tests are against the set of test
196
+ images corresponding to that major/minor release (just in the branch, not
197
+ in master!).
198
+
199
+ 6 . Make sure everything passes the usual CI workflow. Also check the daily or
193
200
weekly "analysis" workflows to make sure there aren't any important
194
201
warnings that should be fixed.
195
202
@@ -330,10 +337,11 @@ Odds and ends to do after the tag is pushed and the announcements are sent:
330
337
- Re-read RELEASING.md and ensure that the instructions match what you
331
338
have done. Update as necessary.
332
339
333
- - Go to readthedocs.org, and ensure that the new release is built and visible.
334
- I tend to keep the latest patch of each minor release available for
335
- reference indefinitely, but hide the docs for earlier patch releases within
336
- that minor release series.
340
+ - Go to readthedocs.org, and ensure that the new release is built and visible
341
+ and is the default release shown (specified in the Admin section). I tend to
342
+ keep the latest patch of each minor release available for reference
343
+ indefinitely, but hide the docs for earlier patch releases within that minor
344
+ release series.
337
345
338
346
- Edit the top-level CMakeList.txt to update the version to the * next*
339
347
anticipated release on the branch, in order to ensure that anybody building
0 commit comments