Release Methodology

From UG

Revision as of 17:10, 20 June 2012 by Alex (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search


About

Release policy

1) Emergency.

Reasons: Urgent bug (UB, example: 3610) or Urgent change (UC:3622). In this case we apply chnage to tag of latest prod release. No code merge required. Code changes are minimal and staging would take max 1-2 days. Could be done on a short notice.

2) Regular.

Normally includes list of DQ tasks (commited to trunk) and project tasks (commited to 1 or more branches). Code merge required. 4 days staging required. We should have release dates set in advance. We should create such releases not too often. Ideally once in 4-8 weeks.

Related Mantis fields

  • RelDate - release date, example: 06/15
  • RNum - release version number, example: 2.24.0
  • RYear - release year, example: 2012
  • ph:
    • Stg - tasks in staging before release
    • Rel - tasks after being released
Retrieved from "https://wiki.jaguarfreight.com/Release_Methodology"
Personal tools