Comment 3 for bug 382678

I think the order things have to happen in is this:

1) Move the current (old) password from the LP tree to its new location that isn't versioned with the rest of Launchpad (where will that new location be, by the way?)

2) After 2.2.6 deploys, commit a change to the new location, changing the password to "foo". Do not deploy it yet.

3) "Simultaneously" update the RT to use the new "foo" password and deploy the change from (2) (which may involve a cherry-pick).

Does this make sense?