Closed runspired closed 8 months ago
cc @HeroicEric for assignment
I looked at whether I could contribute on backport bot
but it appears to backport onto branches - There are no release branches since 3.4 - is this a change of branching methodology?
@BryanCrotaz we only create specific release branch if we have something to backport, so the first backport we create a branch from the tag.
@BryanCrotaz would you be interested in picking up where @Gaurav0 left off with the backport bot?
with #9231 I don't think this particular ticket serves us much use anymore. I would love for use to get a backport bot still, but automating releases is itself a big enough win I'm not sure its worth keeping this open.
The
EmberData
team recently landed a number of improvements to therelease publishing
andCI
pipelines to reduce the cost overhead of releases, enable publishing canary builds tonpm
, and prepare for a more automated future.This ticket outlines remaining work items we hope to accomplish to complete our quest for low-to-zero-overhead releases:
CI
DropWe dropped all jobs we could. Once we have allowed-failure equivalent in gh-actions we will drop the rest.travis.yml
and deactivateTravis
forember-data
Branch Management
backporting bot
feature for backporting fixes tobeta
andrelease
branchesbackporting bot
feature to account for fixes that need to target both beta and release branchesbackporting bot
to work via labelsbackporting bot
should runlint --fix
automatically on backported commitsChangelog Generation
lerna changelog
from custom solutionlerna version
automation step in our release scriptlerna changelog
)Publishing
npm registry
npm
lerna version
prompt for the intended version bumpTesting Automation also means we will want to ensure more robust testing.