Use pbuilder to be extra-sure that the build will succeed in production.

$ cd ..
$ pbuilder-dist raring *dsc

Fix any errors you may discover.

Commit and push.

$ bzr commit
$ bzr push lp:~/[project]/inline-packaging

Then submit your merge proposal and pester (bribing also works) didrocks to review it

Getting it ready for autolanding

Once we have a package that we think is ready for autolanding, there is some checks needed:

Is the unit test suite strong enough so that we ensure we can't regress easily (and automatically ;)) ubuntu? Those tests need to be run in the packaging.

If there are integration tests, is there something like autopilot that we can run on an installed system to automate this run at each landing?

Is debian/changelog still at the latest version in the branch?

If you answered yes to all those questions, congrats! let's get it automatically landing then

Packaging

We need a boostrap commit to know where to start from. The system is then going from bzr tip until that revision to grab all bugs fixed and create a proper changelog with attribution. The form is:

* Automatic snapshot from revision <rrrr> (bootstrap)

<rrrr> can be safely replaced with the bzr commit revision id of the latest release (pushed in ubuntu). This is only for the bootstrap, then, everything is automated. If you don't put it, revision 1 will be taken as a reference.

Setting the component on the stack

Pester didrocks I'll write the instructions in a document properly later on and edit this