TLDR I did a few pr's last week to try and improve / simplify the release and patch process.
#8196
#8202
#8353
#8152
All of those have merged and aren't breaking anything but it hasn't come together to add value yet either.
The idea is that
- our various release processes (nightly, patch, stable etc) should used shared code so we don't have drift on how we're doing things - before it was very copy paste
- releasing, particularly patches, should be as easy as can be and involve little to no human engagement beyond approval.
The current state is
We have the release process from before any of the changes here as a fall back (which is good since i'm not confident in the new stuff)
We have a separate dedicated nightly release job (before it was all in one big file) and that uses the shared action so its not copy pasted
we have a single "promote" job that moves nightly -> preview -> stable all in one go (its not atomic but its more consistent)
we changed the version number scheme to represent better the code (main is preview since thats the code that's there)
we have a new patching process where a /patch comment on a merged pr will generate the correct patches and pr's for approval. it will also auto merge any required version number updates etc.
the docs are all updated.
What i haven't done, is actually got it all to run in the real world. Everything has a 'dry run' flag. I need to do each of hte release types, nightly, promote, patch, as a dry run and see what if anything fails.
TLDR I did a few pr's last week to try and improve / simplify the release and patch process.
#8196
#8202
#8353
#8152
All of those have merged and aren't breaking anything but it hasn't come together to add value yet either.
The idea is that
The current state is
We have the release process from before any of the changes here as a fall back (which is good since i'm not confident in the new stuff)
We have a separate dedicated nightly release job (before it was all in one big file) and that uses the shared action so its not copy pasted
we have a single "promote" job that moves nightly -> preview -> stable all in one go (its not atomic but its more consistent)
we changed the version number scheme to represent better the code (main is preview since thats the code that's there)
we have a new patching process where a /patch comment on a merged pr will generate the correct patches and pr's for approval. it will also auto merge any required version number updates etc.
the docs are all updated.
What i haven't done, is actually got it all to run in the real world. Everything has a 'dry run' flag. I need to do each of hte release types, nightly, promote, patch, as a dry run and see what if anything fails.