Currently Online

Latest Posts

Changes in BzrPrimer

Old Title


Editor Comment

Intitial commit


Revision Differences of Revision 1

# Bazaar primer for SVN developers ¶

This will explain in a shortened workflow how to make the steps from having developed on sf.net and knowing SVN to developing on [launchpad.net](http://launchpad.net) using bazaar (bzr). ¶

## Getting started with bazaar ¶

* Get bazaar: <http://bazaar.canonical.com> or the packaging system of your trust. ¶
* Read <http://wiki.bazaar.canonical.com/BzrForSVNUsers>. ¶

## Getting started with launchpad ¶

* Get an account: <http://launchpad.net> ¶
* Register an SSH key with your account: <https://launchpad.net/people/+me/+editsshkeys>, interesting read is also <https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair> ¶

## Getting started with widelands development ¶

This is for unixes. Windows should work quite similar, but obviously using some kind of GUI like <http://wiki.bazaar.canonical.com/TortoiseBzr>. ¶

~~~~~~ ¶
$ mkdir widelands && cd widelands ¶
$ bzr init-repo . ¶
$ bzr get lp:widelands # This will fetch widelands trunk. ¶
$ cd widelands ¶
hack hack hack ¶
$ bzr commit -m "Commit of a very cool new feature I contributed" ¶
~~~~~~ ¶

The next step varies. If you are a member of [widelands-dev](https://launchpad.net/~widelands-dev) you can directly get your changes back to launchpad: ¶
~~~~~~ ¶
$ bzr push lp:~widelands-dev/widelands/trunk # see the --remember option ¶
~~~~~~ ¶

If you are not a member of [widelands-dev](https://launchpad.net/~widelands-dev), you can still push your changes up to launchpad: ¶
~~~~~~ ¶
$ bzr push lp:~myusername/widelands/cool-new-feature-branch ¶
~~~~~~ ¶

Now, speak up on the [mailinglist widelands-public](https://lists.sourceforge.net/lists/listinfo/widelands-public) and we might merge your branch into trunk if it is good. ¶