How I use it:
I have a directory containing all the OpenERP stuff, which is a Bazaar repository. The structure look as follows:
./7.0-addons # untouched copy of master branch
./7.0-addons-pg_db_schema-redneck # feature branch with changes
./7.0-server # untouched copy of master branch
./7.0-server-pg_db_schema-redneck # feature branch with changes
./addons # fork of master with merged features
./server # fork of master with merged features
Now, after pulling changes from Launchpad to my vendor branches, I run the script (> server/scripts/check_pg_db_schema.sh 7.0-server/openerp 7.0-addons/). If there are relevant changes I will synchronize the relevant feature branches, add some code as said in the bug description, push it to Launchpad and merge the changes into my fork.
I added a Bash script to easily scan for relevant code changes (http:// bazaar. launchpad. net/~openerp- community/ openobject- server/ 7.0-server- pg_db_schema- redneck/ view/head: /scripts/ check_pg_ db_schema. sh).
How I use it:
I have a directory containing all the OpenERP stuff, which is a Bazaar repository. The structure look as follows:
./7.0-addons # untouched copy of master branch pg_db_schema- redneck # feature branch with changes pg_db_schema- redneck # feature branch with changes
./7.0-addons-
./7.0-server # untouched copy of master branch
./7.0-server-
./addons # fork of master with merged features
./server # fork of master with merged features
Now, after pulling changes from Launchpad to my vendor branches, I run the script (> server/ scripts/ check_pg_ db_schema. sh 7.0-server/openerp 7.0-addons/). If there are relevant changes I will synchronize the relevant feature branches, add some code as said in the bug description, push it to Launchpad and merge the changes into my fork.