Release Management Flashcards
What is Release Management?
handles deployments & change initiatives
plan release
manage build through diff environs & stages
^ like uh, mixing & mastering at diff pts/systems during music
testing
deployment
What is Release Management?
giving new shit to custs
costs/budgets/isitValue
improving speed
not fucking up production (stability)
Roles of Release Management
Delivering value to customers
Scalable risk management
Improving deployment efficiency
Software Release Management – Roadmap
Developement > Testing > Build > Maintenance
Tools Used for Release Management
git, come on now
Branch Dynamics in VCS (*)
trunk (main branch) > new work is first committed (maybe dont need to say this part)
create new branch
copy trunk to release branch
tag and actually deploy the branch
maintain the branch
The Release Management Process
► Creating a Release Management System.
Create & enforce checklist
Enforce the checklist
org wide s&p
Software Release Management Activities
distribution outside the regular coding dev work
id-ing, packaging/delivery of releases (think fedex)
has shit for
internal test team
test team (devs, qa, etv)
external test team
cust
when/how do builds happen
makes it at some reg internal (e.g. nightly build)
tags it
there’s a build list
it’s a node on vcs graph
what should be a build be
(a build is combining sci items into correct form, e.g. .exe file)
v Complete – self-sufficient
v Repeatable – automatic, consistent
v Informative – provides feedback
v Schedulable – auto-triggered
v Portable – independent (of IDE)
Build-Package-Deploy Process
(skim this)
Checkout files > prepare build directory > compile > run unit tests > package into JAR and WAR > generate Javadocs, release notes > deploy in test environ > run integration/system tests> distribute
