Environments SVN etc

From UG

Revision as of 15:35, 17 April 2012 (edit) Sasha (Talk | contribs) ← Older edit		Current revision as of 16:15, 5 September 2012 (edit) (undo) Alex (Talk | contribs) (→Environments and location of related code)
(30 intermediate revisions not shown)
Line 1:		Line 1:
	[[Category:Development]]		[[Category:Development]]
-	== 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 ==
-	== UAT Environment ==	+	=== Production ===
-	* '''/branches/uat/2.24.0''' Deployed 12/04/2012	+
		+	* prod: ct.jaguarfreight.com
		+	* SVN prod:
		+	* Version: 2.24.2 (as of 6/26/12)
-	== Staging Environment ==	+	=== Staging Of Production ===
-	* Currently deployed from '''/trunk'''	+
		+	* staging: staging.jaguarfreight.com
		+	* SVN staging:
		+	* Version: 2.25.0 (as of 6/26/12)
-	== Production Releases ==	+	=== DQ ===
-	* '''/tags/2.23.4'''  Released 27/03/2012	+
-	== GMS Feature Development branch ==	+	* dev: dev-kuchma.jaguarfreight.com
-	* '''/tags/2.24.0''' Work in progress	+	* UAT: same
		+	* SVN: '''/trunk'''
-	== Main Development thread ==	+	=== GM Split ===
-	* '''/trunk''' Work in progress	+
		+	* dev: dev.jaguarfreight.com
		+	* UAT: uat.jaguarfreight.com
		+	* SVN: '''/tags/2.24.0'''
		+
		+	=== I Portal ===
		+
		+	* dev: dev3-kuchma.jaguarfreight.com
		+	* UAT: same
		+	* SVN: /branches/InternationalPortal
		+
		+	=== DR/KPI ===
		+
		+	* dev: dev4-kuchma.jaguarfreight.com
		+	* UAT: same
		+	* SVN: /branches/DR_KPI
		+
		+	=== POEM ===
		+
		+	* dev: TBD
		+	* UAT: same
		+	* SVN: /branches/POEM
		+
		+	=== ASN 20 ===
		+
		+	* dev: dev3-kuchma.jaguarfreight.com
		+	* UAT: same
		+	* SVN: /branches/asn2.0
		+
		+	== 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 ==
		+
		+	* [http://svnbook.red-bean.com/en/1.5/index.html Version Control with Subversion]
		+
		+	* [http://techbase.kde.org/Policies/SVN_Commit_Policy 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
		+
		+	* http://nvie.com/posts/a-successful-git-branching-model/

---

Current revision as of 16:15, 5 September 2012

Contents 1 Environments and location of related code 1.1 Production 1.2 Staging Of Production 1.3 DQ 1.4 GM Split 1.5 I Portal 1.6 DR/KPI 1.7 POEM 1.8 ASN 20 2 Misc 2.1 History of Production Releases 2.2 Emergency Release Process 3 Appendix: Definitions, etc. 4 References

[edit] Environments and location of related code

[edit] Production

• prod: ct.jaguarfreight.com
• SVN prod:
• Version: 2.24.2 (as of 6/26/12)

[edit] Staging Of Production

• staging: staging.jaguarfreight.com
• SVN staging:
• Version: 2.25.0 (as of 6/26/12)

[edit] DQ

• dev: dev-kuchma.jaguarfreight.com
• UAT: same
• SVN: /trunk

[edit] GM Split

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

[edit] I Portal

• dev: dev3-kuchma.jaguarfreight.com
• UAT: same
• SVN: /branches/InternationalPortal

[edit] DR/KPI

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

[edit] POEM

• dev: TBD
• UAT: same
• SVN: /branches/POEM

[edit] ASN 20

• dev: dev3-kuchma.jaguarfreight.com
• UAT: same
• SVN: /branches/asn2.0

[edit] Misc

[edit] History of Production Releases

• 27/03/2012 /tags/2.23.4

[edit] 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

[edit] 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".

[edit] 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

• http://nvie.com/posts/a-successful-git-branching-model/