Project

General

Profile

Story #980

Document process for product release cycle

Added by Dave Vieglais about 14 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
Sprint-2010.50
Start date:
2010-10-07
Due date:
% Done:

100%

Story Points:
Sprint:

Subtasks

Task #891: schema change procedureClosedDave Vieglais

History

#1 Updated by Matthew Jones about 14 years ago

Release cycle needs to handle transitions through at least three stages:
a) Development: current active changes to introduce new functionality
b) Staging: test environment
c) Production: versions deployed for external consumption

At each stage, we need to consider how to version and introduce changes in:
a) schemas that define information models
b) APIs that define service and communicaiton interfaces
c) components and libraries that implement a) and b) and that might have dependencies on each other.

#2 Updated by Dave Vieglais about 14 years ago

  • Position set to 5
  • Target version set to Sprint-2010.46
  • Position deleted (31)

#3 Updated by Dave Vieglais about 14 years ago

  • Position deleted (37)
  • Position set to 29
  • Target version changed from Sprint-2010.46 to Sprint-2010.47

#4 Updated by Dave Vieglais almost 14 years ago

  • Target version changed from Sprint-2010.47 to Sprint-2010.48
  • Position deleted (38)
  • Position set to 2

#5 Updated by Dave Vieglais almost 14 years ago

  • Target version changed from Sprint-2010.48 to Sprint-2010.50
  • Position set to 8
  • Position deleted (31)

#7 Updated by Dave Vieglais almost 14 years ago

  • Status changed from New to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)