Community mailing list archives

Re: OCB 8.0 - pulling updates best practice

- 10/16/2014 05:13:12
Since v6 we found that pulling Odoo updates (or even upgrading unrelated Ubuntu packages) more than once a month was disruptive. A regression can always happen, you need to have the resource to fix it fast.
So instead, we finally set up a test server that users can connect to, where we semi-automatically pull odoo, OCB and our own patches, and restore+upgrade a copy of the production database.
Then when users give us a green light, we plan a proper deployment.

Users also like the test server because it lets them try things they are not sure about, without breaking anything in production.


Le 16/10/2014 10:52, Gunnar Wagner a écrit :
<blockquote cite="" type="cite">

We are using OCB 8.0 (cloned from github) as a users (not developing or reviewing nor any other kind of involvement in the making).
I am updating our local installation with git pull origin 8.0 and wonder what would be a good practice regarding frequency of this pulling exercise.

Concrete I mean is it advisable to either:

  • process a "git pull" often (assuming at present there will be new commits pretty frequent)    or

  • process it only rarely (and then probably pulling several commits in one pull)

any advice/opinion regarding this is highly appreciated 

thanks & best ...Gunnar

Post to: