oship-dev team mailing list archive

[Eduardo César <xcesar@xxxxxxxxx>]

Hi Roger,

Thank you. For the benefit of all people not so perceptive like the devs we
have here, I will add some more information, the best way I can, even though
in English:

- Some background about the 2a format, the last version of the format used
in the metadata of bzr:
https://medsphere.org/community/project/openvista-server/blog/2010/04/16/bazaar-repository-formats

- Upgrade information
http://wiki.bazaar.canonical.com/FormatUpgrades

- Your local branch:
The only thing needed is to perform the upgrade in the local branch of the
developer, by running "bzr upgrade --format", OR getting a new trunk from
the launchpad repository.

- Other branches:
At first, the idea is to NOT upgrade them. The stable branch is not being
actively commited like the trunk. and the benefits to do so are little. And
then there is the question that it is the "stable" branch. I think that we
can push and experiment a little with the trunk, and now that we undergone a
major trunk change, it can be a good time to upgrade the format too.

- The tests
Well, the previous email was mainly focused on the tests, and I invite
anyone that are interested in the tests to look at it.

- What will be done:
Upgrading the trunk to the new format, 2a

- Why is that:
I proposed the new format because I could not have a local shared repository
in the old format, so to have more than one branch locally, I must copy all
the redundant metadata of one to another, and, in the current state of
oship, the metadata is even bigger that the working tree. Basically, what
would be done is the creation of one set of revisions and multiple working
trees. One will be a exact copy of the trunk and the others would be used
for development, in a self-containing way. One of the benefits if this type
of developing style is that the trunk tend to be more stable, because added
features of bug correction can be done on its own trunk.

- How it will be done:
Pressing the upgrade button in the launchpad interface:

- Who will do that:
I will, but any dev can do that. Its probably because I had proposed the
upgrade.

- When it will be done:
The plan is to do it on saturday, to give time to everyone to express their
concerns about it. If needed, it  will be delayed so all the parties
involved can work together to ensure all can be nice and smooth in the
transition and to be reassured that we can count on each other.

Cheers
Eduardo