Hi, Thanks will have a look at the openerp-tools repo.
Why would 7.0 stable branch introduce incompatibilities? It doesn't make sense. Most open source projects tag/branch a release and then only bug fixes get back ported into that, while features go into trunk, to become 7.0.1 a few weeks later, or whatever. Why do openerp do it this way? Debs is what all open source projects use for production (on debian and friends), again, why do openerp recommend version control? Debs are meant to make sys admin for upgrades etc easier. We're using the debs, and they work well, how has bzr saved your life in a way that the nightly debs couldn't? On Mon, 4 Mar 2013 07:59:32 -0430 Nhomar Hernández <[email protected]> wrote: > Hello > > Scripts I think are in lp:openerp-tools where there are all thing > related to openerp automation things I openerps servers. > > About compatibilty, theorically they are, after any update dont > forgat do a -u all -d database as parameters to allow update strings > and some things in views. > > My best recomendatio is use bzr to control your production servers > it has saved my life several times. > > Regards. > > Written from my android > On Mar 4, 2013 7:55 AM, "Hiren" <[email protected]> wrote: > > > > > Hi all, > > > > We run a prod system using the nightly deb repo, I wanted to > > confirm, any new nightly builds (and therefore debs) are meant to > > stay backward compatible to previous 7 nightly builds right? > > Outright field changes and things that will break custom modules or > > customizations will not happen with the nightlies right? > > > > The nightlies we're using are from: > > http://nightly.openerp.com/7.0/nightly/deb/ > > > > I can't find the script that builds the nightlies anywhere in the > > repo's, I take it the above link is built from 7.0's branch? and not > > trunk? The download page on the website mentions 7.0 stable and > > points to this same nightly link. > > > > While on the stable upgrade topic, once a deb based update is done > > to a newer build, is openerp-server -d <DB> -a all meant to be > > done? Or is it not necessary? The deb postinst script does not run > > this, is it needed at all? > > > > Thanks. > > > > -- > > Hiren > > [email protected] > > > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openerp-expert-framework > > Post to : [email protected] > > Unsubscribe : https://launchpad.net/~openerp-expert-framework > > More help : https://help.launchpad.net/ListHelp > > -- Hiren [email protected] _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
