Environments SVN etc

From UG

Revision as of 18:57, 27 May 2012 (edit) Alex (Talk | contribs) (→Environments and location of related code) ← Older edit		Revision as of 18:57, 27 May 2012 (edit) (undo) Alex (Talk | contribs) (→Production Releases) Newer edit →
Line 49:		Line 49:
	== Misc ==		== Misc ==
-	=== Production Releases ===	+	=== History of Production Releases ===
-	* 27/03/2012 '''/tags/2.23.4'''	+	* 27/03/2012 '''/tags/2.23.4'''
	=== Emergency Release Process ===		=== Emergency Release Process ===

---

Revision as of 18:57, 27 May 2012

Contents 1 About 2 Environments and location of related code 2.1 Production 2.2 Staging Of Production 2.3 DQ 2.4 GM Split 2.5 I Portal 2.6 DR/KPI 2.7 POEM 3 Misc 3.1 History of Production Releases 3.2 Emergency Release Process 4 Appendix: Definitions, etc. 5 References

About

This wiki is to log what SVN tag/branch is associated with what project/environment.

Please keep it updated!

Environments and location of related code

Production

• prod: ct.jaguarfreight.com
• SVN prod:

Staging Of Production

• staging: staging.jaguarfreight.com
• SVN staging:

DQ

• dev: ???
• UAT: same
• staging:
• SVN: /trunk Work in progress

GM Split

• dev: ???
• UAT: uat.jaguarfreight.com
• SVN: /tags/2.24.0

I Portal

• dev: dev3-kuchma.jaguarfreight.com
• UAT: same
• SVN: ???

DR/KPI

• dev: dev4-kuchma.jaguarfreight.com
• UAT: same
• SVN: /branches/DR_KPI

POEM

• dev: dev5-kuchma.jaguarfreight.com
• UAT: same
• SVN:

Misc

History of Production Releases

• 27/03/2012 /tags/2.23.4

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".

References

• Version Control with Subversion

• KDE Commit Policy

• https://wiki.openmrs.org/display/docs/Subversion+Branching+and+Merging+Techniques

• http://stackoverflow.com/questions/464417/how-to-use-svn-branch-tag-trunk

• http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html