On Fri, Feb 01, 2013 at 03:22:42PM +1300, Michael Hudson-Doyle wrote: > Hi gang, > > I've just deployed a long-awaited change: we can (and do) now deploy > components such as lava-dispatcher from bzr branches. If you look at > the new buildout configuration files: > > http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head:/buildout.cfg#L127 > http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head:/buildout-production.cfg#L37 > > I hope it's reasonably self-explanatory what's going on: lines like > > lava-dispatcher = lp:lava-dispatcher > > in [branches] section says "satisify a requirement for the egg > lava-dispatcher from the branch at lp:lava-dispatcher". > > Lines like > > lava-dispatcher = 551 > > in the [revisions] section -- only present in the locked-down > buildout-production.cfg -- specify which revision to use. So when you > want to deploy a fix to production, no need to futz with pypi and tags > and post release bumps -- just push to trunk, update the revno in > buildout-production.cfg and run lava-deployment-tool update!
We don't need to to post-release bumps, but we still need to manage the version numbers, right? Or are we stablishing that the bzr revision is the version number now? -- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org
signature.asc
Description: Digital signature
_______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
