deploymentprocedure
Differences
This shows you the differences between two versions of the page.
|
deploymentprocedure [2010/07/23 16:55] elyoliveira angelegt |
deploymentprocedure [2012/10/30 10:27] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Testing | + | ===== Deployment of new Features ===== |
| + | |||
| + | On this page we describe the procedure for deploying new features on the web application. | ||
| + | |||
| + | 1. The developers have until Fridays 10:00 AM to prepare the new features that will be deployed on production. The preparation comprises the following steps. | ||
| + | * Test the implementation. | ||
| + | * Push it to the central repository. | ||
| + | * Update the [[FeatureArrivals]] list. | ||
| + | * Provide the deployment instructions. | ||
| + | * Mark its status as Landing. | ||
| + | |||
| + | 2. Every Friday, between 10:00 AM and 11:00 AM, all Landing features are deployed on the production environment. The administrator takes the following steps. | ||
| + | * Collect all new features pushed to the central repository during the past week. | ||
| + | * Deploy them on production, following the instructions provided by the developers. | ||
| + | * Update the [[FeatureArrivals]] list. | ||
| + | * Mark its status as Grounded. | ||
| + | * Inform the same target release for all device features deployed on that day. | ||
deploymentprocedure.1279896949.txt.gz · Last modified: 2012/10/30 10:35 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
