deploymentprocedure
Differences
This shows you the differences between two versions of the page.
|
deploymentprocedure [2010/07/26 10:57] elyoliveira |
deploymentprocedure [2012/10/30 10:27] (current) |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * Test the implementation. | * Test the implementation. | ||
| * Push it to the central repository. | * Push it to the central repository. | ||
| - | * Inform how it can be deployed on production at the column Deployment at the [[FeatureArrivals]] list. This information includes not only files to be copied to the production environment but also configurations to be made in Drupal such as user rights and translations. | + | * Update the [[FeatureArrivals]] list. |
| - | * Mark its status as Landing at 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. | 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. | * Collect all new features pushed to the central repository during the past week. | ||
| * Deploy them on production, following the instructions provided by the developers. | * Deploy them on production, following the instructions provided by the developers. | ||
| - | * Mark its status as Grounded at [[FeatureArrivals]] list. | + | * Update the [[FeatureArrivals]] list. |
| + | * Mark its status as Grounded. | ||
| + | * Inform the same target release for all device features deployed on that day. | ||
deploymentprocedure.1280134671.txt.gz · Last modified: 2012/10/30 10:42 (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
