mvhub-dev team mailing list archive

[noreply@xxxxxxxxxxxxx]

Merge authors:
  Lee Goodrich (leegoodrich)
------------------------------------------------------------
revno: 376 [merge]
committer: Lee Goodrich <lgoodrich@xxxxxxxxxx>
branch nick: trunk
timestamp: Mon 2010-05-03 16:45:15 -0400
message:
  merged improve_production_docs
modified:
  app-mvhub/doc/checklists/move_to_production.txt


--
lp:mvhub
https://code.launchpad.net/~mvhub-commit/mvhub/trunk

Your team MVHub Developers is subscribed to branch lp:mvhub.
To unsubscribe from this branch go to https://code.launchpad.net/~mvhub-commit/mvhub/trunk/+edit-subscription

=== modified file 'app-mvhub/doc/checklists/move_to_production.txt'
--- app-mvhub/doc/checklists/move_to_production.txt	2010-04-23 21:18:30 +0000
+++ app-mvhub/doc/checklists/move_to_production.txt	2010-05-03 20:43:48 +0000
@@ -15,13 +15,16 @@
 	
 	# for a regular scheduled release the 
 	# minor release number is 00
+	
+	# For any small, unplanned changes (like critical bug fixes)
+	# use the existing MAJOR_RELEASE_NUM and increment MINOR_RELEASE_NUM
 
 	export MINOR_RELEASE_NUM='00'
 
 ___ Determine release tag
 	
 	export RELEASE_TAG="$MAJOR_RELEASE_NUM-$MINOR_RELEASE_NUM"
-	
+
 ___ Create the release
 	
 	# Navigate to trunk branch
@@ -44,10 +47,10 @@
 		
 		__ update changelog
 			$EDITOR Changes
-
+       
 	___ commit changes
 
-		bzr commit -m 'updated Changelog , set $VERSION for CPAN'
+		bzr commit -m 'RELEASE: updated Changelog , set $VERSION for CPAN'
 
 	___ Tag the most recent revision as release
 	
@@ -56,33 +59,33 @@
 		# Push the release branch to Launchpad
 	 	bzr push
 
-___ Export the release
-	
-	bzr export ../$RELEASE_TAG -rtag:$RELEASE_TAG
-
-___ Import the release into the release branch
-
-	cdws
-	cd release
-	bzr pull
-	bzr import ../$RELEASE_TAG
-
-___ Commit changes & push branch to launchpad
-
-	bzr commit -m "$RELEASE_TAG Major Release"
-
-	# Import/Export strips the tag, so it needs to be recreated
-	bzr tag $RELEASE_TAG
-	
-	# Push release revision to launchpad
-	bzr push
+___ Export the release as a tarball
+	
+	bzr export ../mvhub_$RELEASE_TAG.tar.gz -rtag:$RELEASE_TAG
+
+___ Create a Release on Launchpad.net
+	
+	Firefox: https://launchpad.net/mvhub/trunk/+addrelease
+	# Fill out information for release, picking the appropriate
+	# Milestone or creating a new one if an appropriate one doesn't
+	# already exists.
+
+
+___ Attach tarball to Release on Launchpad.net
+
+	Firefox: https://launchpad.net/mvhub/trunk
+	# Click on the Release name you just created near the bottom of 
+	# the screen. On the next page click the "Add download File" link.
+	# Fill out the forms and navigate to the location of the tarball
+	# that was created previously. Click 'upload' to finish.
+	
 
 ___ Test the release in Staging
 
 	___ Pull the new release into Staging
 		
 		ssh staging.inside
-		cd /var/www/mvhub/www-data/source-code/release
+		cd /var/www/mvhub/www-data/source-code/trunk
 		sudo su www-data -c "bzr pull"
 
 	___  put production data into staging database
@@ -97,13 +100,12 @@
 		# where yyyy is year mm is 2 digit month, etc, etc
 		ls /var/backups/postgres/
 		
-		scp /var/backups/postgresql/<latest dump file>.sql \
-			pengiun.inside
+		scp /var/backups/postgresql/<latest dump file>.sql pengiun.inside
 
 		ssh staging.inside
 		# import production data
         
-        psql -h localhost -U staging -d staging.nsp -f \
+        psql -h localhost -U www-data -d www-data.nsp -f \
              $LATEST_DUMP_FILE.sql > /dev/null
 		
 		# After executing the previous command, you may recieve three
@@ -113,11 +115,11 @@
 	____ handle schema changes
 
 	____run mv_setup to handle conf file changes
-		ssh staging.inside
 		sudo su www-data -l
 		cdw
 		
-		# DO NOT DESTROY DATABASE. IT WILL NUKE PRODUCTION DATA!
+		# DO NOT DESTROY DATABASE. That will undo the import of the
+		# production data in previous step.
 		mv_setup
 		
 	____ (***IF*** apache conf has changed) test new apache conf w/ staging user 
@@ -139,15 +141,14 @@
 
 	___ update release branch in production
 		ssh production.inside
-		cd  /var/www/mvhub/www-data/source-code/release/
+		cd  /var/www/mvhub/www-data/source-code/trunk/
 		sudo su www-data -c 'bzr pull'
 	
 	___ run mv_setup to handle conf file changes
 		sudo su www-data -l
 		cdw
 		
-		# DO NOT DESTROY DATABASE. That will undo the import of the
-		# production data in previous step.
+		# DO NOT DESTROY DATABASE. IT WILL NUKE PRODUCTION DATA!
 		mv_setup
 		
 	___ (if needed) replace apache config