User Tools

Site Tools


deploymentprocedure

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

deploymentprocedure [2010/07/23 17:27]
elyoliveira
deploymentprocedure [2012/10/30 10:27] (current)
Line 3: Line 3:
 On this page we describe the procedure for deploying new features on the web application. 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 features that will be deployed on production. +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. 
-The preparation involves testing the implementation, and pushing the changes to the central repository.+  * 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 features marked with status Landing are deployed on the production environment. +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. 
-The administrator collects all new features pushed to the repository during the past week and installs them on production.+  * 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.1279898859.txt.gz · Last modified: 2012/10/30 10:36 (external edit)