 |
|
 |
|
Some policies are simple honest best practice and we suggest you maintain three branches to cover separation of completed releasable and deployable code from development code, to ensure proper versioning and release capability. For this separation you will suitably establish a Development Branch, a Release Branch and a Deployment Branch. If you keep your code evidently distinct and separate, it is less likely you will have code corruption accidents.
So, in this way you have one branch for each major project environment. Development is conducted in the Development Branch and releases are committing to the other branches. An assessment is performed on your code before committing to the Release or Deployment branches. The assessment is simple. You will validate that the code is stable for that environment.
The assessment is done in collaboration with the release manager and branch acceptance criteria will be satisfied in order to successfully pass the assessment. The assessments will increase in severity and complexity as code progresses from Development, to Release and to the Deployment Branch for final deployment onto the live environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
Glossary: »
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
|
|
|
|
|
|
|
|
|
|
| | |
| | |
|
 
 SPADE: Successful Pragmatic Agile Delivery Everytime™ |
| Topic: 314 Page: 266/444 Progress: 59.9% |
 | |
|
|
|
|
|
|
|
|
This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL (http://www.bigagiletoolkit.com/) and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™
All rights reserved. |
|
