Release Management and Deployment with Distributed Version Control System Training Course
Duration
Requirements
Familiarity with GIT is recommended.
Understanding of software development life cycle, project management methodologies and frameworks (like waterfall and Agile) is required.
Public Course Dates
Then just submit a public course date request now!
And we will organize the training at a location and date to suit you.
Request Public Course Date >>
| Date | Venue | Price | ||
|---|---|---|---|---|
| 2012-06-07 09:30 | London, Westbourne Grove | From 900 to 1290 GBP Check! | ||
| 2012-06-11 09:30 | Bristol, Temple Gate | From 900 to 1290 GBP Check! | ||
| 2012-06-13 09:30 | Manchester | From 900 to 1290 GBP Check! | ||
| 2012-07-11 09:30 | Manchester | From 900 to 1290 GBP Check! | ||
| 2012-07-12 09:30 | Bristol, Temple Gate | From 900 to 1290 GBP Check! | ||
| 2012-07-20 09:30 | London, Westbourne Grove | From 900 to 1290 GBP Check! | ||
| 2012-08-02 09:30 | Bristol, Temple Gate | From 810 to 1161 GBP Check! | ||
| 2012-08-30 09:30 | London, Westbourne Grove | From 810 to 1161 GBP Check! | ||
| 2012-08-31 09:30 | Manchester | From 810 to 1161 GBP Check! | ||
| 2012-09-05 09:30 | Bristol, Temple Gate | From 810 to 1161 GBP Check! |
Overview
This course has been created for project managers, release managers, product managers, product owners, Scrum Masters, software architects and everyone who is responsible for planning releases and deployment of software.
It shows how to move changes from requirements, through development and tests to production environment using distributed version control system (GIT in particular, but people using other distributed SCMs can benefit from this course as well).
Course Outline
Show overview of Project Management methodologies
- Agile Methodologies
- Waterfall
Automatic deployment via GIT
- Production repository
- Release branch
- Using Tags for releases
- Switching between releases
- Managing maintenance release
- Major releases
Documentation, Release Change Log
- Using Repository History to create Change Log
- Using Tag description for major release summarising changes
- Aggregating smaller changes into bigger one (closer to the business)
- Aggregating commits
- Grouping commits into logical parts
Central Repo Push and Pull Strategies
- Keeping Central repository clean
- Creating structure for aggregating and reviewing changes from developers
- Testing and Staging environment
Software Architecture and Components
- How to divide logically application and the repository
- How to manage libraries and subprojects develop by third parties
- Using submodules to automate upgrades

