canmove, Confirmed users
457
edits
Services/Process/ServerReleaseProcess: Difference between revisions
Services/Process/ServerReleaseProcess (view source)
Revision as of 20:28, 19 April 2011
, 19 April 2011no edit summary
m (Created page with "= Introduction = This is a proposed Services Release Process. In the spirit of having time based releases, the goal of this process is to have a set interval when server side cha...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
This is | This is the Server Release Process for the Services team. In the spirit of having time based releases, the goal of this process is to have a set interval when server side changes are pushed to production. This is to drive a consistent and predictable flow of changes on the server side. We will start with a weekly push and refine the process as we go. | ||
= Sequence of events = | = Sequence of events = | ||
| Line 38: | Line 38: | ||
** Coordination with client for features that require it - Answer: jarguello will a dependency line between the two. Probably in the feature page. | ** Coordination with client for features that require it - Answer: jarguello will a dependency line between the two. Probably in the feature page. | ||
** How about a push to stage first, giving us a cascaded release that we can, e.g., run CrossWeave against? - Answer: jarguello spoke to test and they will do this type of verification as part of their testing in staging. | ** How about a push to stage first, giving us a cascaded release that we can, e.g., run CrossWeave against? - Answer: jarguello spoke to test and they will do this type of verification as part of their testing in staging. | ||
** Will the hand offs be recorded in e-mails or in the bugs themselves? | |||