upgrade --2a for some projects

Asked by Julien Thewys on 2010-02-10

Hi,

We are willing to upgrade some of our projects branches to the latest repository format (2a), mostly to reduce the size of the repositories.

We would like to know how smoothly this conversion can be achieved if done by the Launchpad team.
In particular:
 * How should we plan this process with the Launchpad team? (timing, should the owner make the request,...)
 * Are the repositories inaccessible during the upgrade or is it some sort of double buffering?

Here is a provisional list of branches that need to be upgraded:
    lp:~openerp/openerp/package-script

    lp:~openerp/openobject-server/trunk
    lp:~openerp/openobject-client/trunk
    lp:~openerp/openobject-client-web/trunk
    lp:~openerp/openobject-addons/trunk
    lp:~openerp/openobject-addons/trunk
    lp:~openerp-commiter/openobject-addons/trunk-extra-addons

    lp:~openerp/openobject-server/5.0
    lp:~openerp/openobject-client/5.0
    lp:~openerp/openobject-client-web/5.0
    lp:~openerp/openobject-addons/5.0
    lp:~openerp/openobject-addons/5.0
    lp:~openerp-commiter/openobject-addons/5.0-extra-addons

Thank you,
--
Julien Thewys

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Michael Hudson-Doyle
Solved:
2010-10-31
Last query:
2010-10-31
Last reply:
2010-02-11

In the cases where you're not using stacking, the "upgrade this branch" link on the bottom of each page can be used safely. The branch will not be locked during the conversion, it is done off to the side and then any revisions pushed during the conversion are pulled in.

Where you are using stacking, it's best to upgrade the stacked branch before the stacked-on branch. The stacked branch will be unusable until the stacked-on branch is upgraded though.

Hope this helps.

Julien Thewys (julien-thewys) said : #2

Thanks Michael Hudson-Doyle, that solved my question.