Script-assisted release process #1421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
looks like the script proposals are accidentally conflated with your staged release branch? |
|
Intentionally. Will rebase after landing that. |
ssteinbach
force-pushed
the
main.release.automated_release_proposal
branch
from
040f7a1
to
666f334
Compare
ssteinbach
force-pushed
the
main.release.automated_release_proposal
branch
from
666f334
to
38c16dd
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1421 +/- ##
=======================================
Coverage 86.08% 86.08%
=======================================
Files 201 201
Lines 21051 21051
Branches 2461 2461
=======================================
Hits 18121 18121
Misses 2328 2328
Partials 602 602
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Merged
ssteinbach
changed the title
MichaelPlug
pushed a commit
to MichaelPlug/OpenTimelineIO
that referenced
this pull request
Aug 5, 2023
) * clean up verify license * fix licenses in place * add license to examples * freeze ci version script * lint pass * add make targets for making a release and starting a new dev cycle * update fetch_contributors so that it updates the CONTRIBUTORS.md * adding in bump version number script * dev1 stripping/appending script * add confirmation to makefile * omit the otio-version json from the packages * rename bump version target to be specific to minor version bumps * add shuffle verison map * add dev-suffix target * add test-core Co-authored-by: ssteinbach <[email protected]> Signed-off-by: Michele Spina <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Making an OTIO release is a lot of work. In order to streamline the process, I've started a series of incredibly hacky single purpose python scripts (and adapted others that had already been written), tying them together with a single make target.
The goal is that the process could boil down to:
make releasemake start-new-versionThis is a draft PR and will be rebased post landing the release and ideally used to start v0.16.0.