Dear all,

There is one issue with the combination of Trac and Bazaar because of their quite different natures. Trac is a centralized system, whereas Bazaar is a decentralized one. bzr.calitko.org is a central location where Calitko developers can push their revisions to but the way developers manage their public directories at bzr.calitko.org is totally “decentralized”. Branches can be created and deleted, renamed, overwritten.

For example, I had branched Petr’s dev branch and implemented the initial Uri version in my local branch. The Petr merged my branch and continued development using the new class. Then I wanted to add an additional test for class Uri and instead of merging again I decided to bzr pull –overwrite my local Uri branch with Petr’s latest revision and then push it to my public location. Essentially I deleted my local and public branches and created them again. Hence the revision numbers at developers/peter/calitko-petr changed and some references from Source Talk or from tickets (if such existed) could have become broken or incorrect. The revisions themselves are not lost - if a revision has ever been merged it is kept but is not directly visible. bzr log lists all merged revisions and you will notice the dotted revision number (e.g. revno 118.1.4).

The point is that we cannot really rely on rev numbers much. The only revision numbers that have a very high change to remain constants are the revnos of the official Calitko branch. The question arises how do we refer to revisions? Especially to revisions that are not yet, and possibly never going to be merged to the main branch?

Ideas?

Regards,

Peter