Environments SVN etc
From UG
(Difference between revisions)
(→I Portal) |
(→Main Development thread) |
||
| Line 23: | Line 23: | ||
* '''/tags/2.24.0''' Work in progress | * '''/tags/2.24.0''' Work in progress | ||
| - | == | + | == DQ == |
| - | * '''/trunk''' Work in progress | + | * dev: |
| + | * UAT: | ||
| + | * Subv: '''/trunk''' Work in progress | ||
== Emergency Release Process == | == Emergency Release Process == | ||
Revision as of 16:21, 25 May 2012
Contents |
About
This wiki is to log what SVN tag/branch is associated with what project/environment.
Please keep it updated!
I Portal
- dev envir: dev3-kuchma.jaguarfreight.com
- UAT envir: same
- SVN: ???
UAT Environment
- 12/04/2012 /branches/uat/2.24.0
Staging Environment
- 17/04/2012 /tags/2.23.5 - tag for Emergency Release on 18/04/2012 (mantis numbers 3540 and 3529)
Production Releases
- 27/03/2012 /tags/2.23.4
GMS Feature Development branch
- /tags/2.24.0 Work in progress
DQ
- dev:
- UAT:
- Subv: /trunk Work in progress
Emergency Release Process
- field
- before task is forwarded to coding (ph is set to Dev) field
- Staging/System Integration QA
- Dev. Manager (KU/Sa) with Release Manager (Roma) must analyze what type of staging (integration testing) is required for particular Emerg. Release, estimate and request appropriate number of days / hours
- only affected components must be tested
Appendix: Definitions, etc.
The trunk is the main line of development in a SVN repository.
A branch is a side-line of development created to make larger, experimental or disrupting work without annoying users of the trunk version. Also, branches can be used to create development lines for multiple versions of the same product, like having a place to backport bugfixes into a stable release.
Finally, tags are markers to highlight notable revisions in the history of the repository, usually things like "this was released as 1.0".
