Merge lp:~gary/juju-gui/moredocs into lp:juju-gui/experimental

[Gary Poster]

Document staging release problem workarounds

I encountered two problems working with the staging site and releases. These changes document the problems and the solutions I found.

https://codereview.appspot.com/7278054/

[Gary Poster (gary)]

Reviewers: mp+146492_code.launchpad.net,

Message:
Please take a look.

Description:
Document staging release problem workarounds

I encountered two problems working with the staging site and releases.
These changes document the problems and the solutions I found.

https://code.launchpad.net/~gary/juju-gui/moredocs/+merge/146492

(do not edit description out of merge proposal)

Please review this at https://codereview.appspot.com/7278054/

Affected files:
   A [revision details]
   M docs/process.rst

[lp:~gary/juju-gui/moredocs]

367. By Gary Poster on 2013-02-04

reinstate some nice bits I inadertently stomped on

[Gary Poster (gary)]

Please take a look.

https://codereview.appspot.com/7278054/

[Gary Poster (gary)]

Self-reviewing.

https://codereview.appspot.com/7278054/

[Gary Poster (gary)]

*** Submitted:

Document staging release problem workarounds

I encountered two problems working with the staging site and releases.
These changes document the problems and the solutions I found.

R=
CC=
https://codereview.appspot.com/7278054

https://codereview.appspot.com/7278054/

=== modified file 'docs/process.rst'
--- docs/process.rst	2013-02-01 17:34:34 +0000
+++ docs/process.rst	2013-02-04 18:58:19 +0000
@@ -176,21 +176,43 @@
 - Also do the same checks after running the command ``NO_BZR=1 make debug``.
 - For now, we will assume you would like to verify the release on the
   Launchpad staging server.  As we become more confident with this process,
-  this step may become unnecessary.  In the branch, run ``FINAL=1 make
-  dist``.  This will step you through signing the tarball, connecting to
-  Launchpad, and uploading the release.
-
-  - If you have two-factor authentication enabled on Launchpad, the staging
-    server will ask for a one-time password: be sure to have your device
-    available. (If you are a Canonical collaborator, you may try and ask the
-    webops to turn off the two-factor authentication on your Launchpad staging
-    account, but it may not be possible anyway. Go to the ``#u1-as`` channel
-    on the Canonical IRC server and ask something like "webops, could you
-    disable 2FA on my staging account?")
-  - When Launchpad asks you what level of permissions to grant, assuming you
-    are running on your own computer that you manage securely, the easiest
-    thing to do is hopefully also reasonably safe: accept that the computer
-    may perform all actions, indefinitely.
+  this step may become unnecessary.
+
+  - In the branch, run ``FINAL=1 make dist``.  This will step you through
+    signing the tarball, connecting to Launchpad, and uploading the release.
+
+    - If you have two-factor authentication enabled on Launchpad, the staging
+      server will ask for a one-time password: be sure to have your device
+      available. (If you are a Canonical collaborator, you may try and ask the
+      webops to turn off the two-factor authentication on your Launchpad
+      staging account, but it may not be possible anyway. Go to the ``#u1-as``
+      channel on the Canonical IRC server and ask something like "webops,
+      could you disable 2FA on my staging account?")
+    - When Launchpad asks you what level of permissions to grant, assuming you
+      are running on your own computer that you manage securely, the easiest
+      thing to do is hopefully also reasonably safe: accept that the computer
+      may perform all actions, indefinitely.
+    - If you get a complaint that the "juju-gui" project does not exist, you
+      have an invalid cached Launchpad token. This will most often happen
+      because the staging database has been reset, so your local machine
+      thinks it has a valid token but the staging version of Launchpad has
+      forgotten it.  This error also may happen if you go to Launchpad and
+      explicitly revoke your token's authorization at
+      https://staging.launchpad.net/people/+me/+oauth-tokens (or, if you are
+      encountering this problem on the main, non-staging Launchpad site,
+      https://launchpad.net/people/+me/+oauth-tokens).  To resolve, remove the
+      token from your local machine.  On Ubuntu desktop machines, this can be
+      done by opening the Seahorse password manager (search the dash for
+      "seahorse" or "password"), looking for a password identified as
+      "Password for 'System-wide:
+      Ubuntu(...)@https://api.staging.launchpad.net/ on 'launchpadlib'" (try
+      filtering for "staging.launchpad"), right-clicking on it, and choosing
+      "Delete."
+    - If you get an ERR_CANNOT_FORWARD 115 error from Squid when you try to
+      run the script, it probably is because the Launchpad server is updating.
+      Go to <https://staging.launchpad.net/> to verify.  Try again when
+      Launchpad is back online.
+
   - Go to <https://staging.launchpad.net/juju-gui/stable> and verify that you
     see a new release and a new download file.
   - Download the file and compare it to the original tarball in the
@@ -263,21 +285,43 @@
 - Also do the same checks after running the command ``NO_BZR=1 make debug``.
 - For now, we will assume you would like to verify the release on the
   Launchpad staging server.  As we become more confident with this process,
-  this step may become unnecessary.  In the branch, run ``make dist``.
-  This will step you through signing the tarball, connecting to
-  Launchpad, and uploading the release.
-
-  - If you have two-factor authentication enabled on Launchpad, the staging
-    server will ask for a one-time password: be sure to have your device
-    available. (If you are a Canonical collaborator, you may try and ask the
-    webops to turn off the two-factor authentication on your Launchpad staging
-    account, but it may not be possible anyway. Go to the ``#u1-as`` channel
-    on the Canonical IRC server and ask something like "webops, could you
-    disable 2FA on my staging account?")
-  - When Launchpad asks you what level of permissions to grant, assuming you
-    are running on your own computer that you manage securely, the easiest
-    thing to do is hopefully also reasonably safe: accept that the computer
-    may perform all actions, indefinitely.
+  this step may become unnecessary.
+
+  - In the branch, run ``make dist``. This will step you through signing the
+    tarball, connecting to Launchpad, and uploading the release.
+
+    - If you have two-factor authentication enabled on Launchpad, the staging
+      server will ask for a one-time password: be sure to have your device
+      available. (If you are a Canonical collaborator, you may try and ask the
+      webops to turn off the two-factor authentication on your Launchpad
+      staging account, but it may not be possible anyway. Go to the ``#u1-as``
+      channel on the Canonical IRC server and ask something like "webops,
+      could you disable 2FA on my staging account?")
+    - When Launchpad asks you what level of permissions to grant, assuming you
+      are running on your own computer that you manage securely, the easiest
+      thing to do is hopefully also reasonably safe: accept that the computer
+      may perform all actions, indefinitely.
+    - If you get a complaint that the "juju-gui" project does not exist, you
+      have an invalid cached Launchpad token. This will most often happen
+      because the staging database has been reset, so your local machine
+      thinks it has a valid token but the staging version of Launchpad has
+      forgotten it.  This error also may happen if you go to Launchpad and
+      explicitly revoke your token's authorization at
+      https://staging.launchpad.net/people/+me/+oauth-tokens (or, if you are
+      encountering this problem on the main, non-staging Launchpad site,
+      https://launchpad.net/people/+me/+oauth-tokens).  To resolve, remove the
+      token from your local machine.  On Ubuntu desktop machines, this can be
+      done by opening the Seahorse password manager (search the dash for
+      "seahorse" or "password"), looking for a password identified as
+      "Password for 'System-wide:
+      Ubuntu(...)@https://api.staging.launchpad.net/ on 'launchpadlib'" (try
+      filtering for "staging.launchpad"), right-clicking on it, and choosing
+      "Delete."
+    - If you get an ERR_CANNOT_FORWARD 115 error from Squid when you try to
+      run the script, it probably is because the Launchpad server is updating.
+      Go to <https://staging.launchpad.net/> to verify.  Try again when
+      Launchpad is back online.
+
   - Go to <https://staging.launchpad.net/juju-gui/trunk> and verify that you
     see a new release and a new download file.
   - Download the file and compare it to the original tarball in the