Thursday, 17 May 2012

Working with branch in OpenERP,branch

Create Branch-name:
1) tiny@tiny:~/workspace/rdtools$ make branch-trunk-feature
                    # create a branch to work on a single feature on trunk
                  python branch-trunk-feature

2) author (eg : tfr): pna

3) launchpad project (1 : addons, 2 : client, 3 : client-web, 4: server) : 1

4) feature name: hr_job_imp
                bzr branch lp:~openerp/openobject-addons/trunk addons/trunk-hr_job_imp-pna
               Branched 6792 revision(s).
               bzr push -d addons/trunk-hr_job_imp-pna lp:~openerp-dev/openobject-addons/trunk-

5) tiny@tiny:~/workspace/rdtools$ make pull  

Get Patch :

        $ >   bzr diff >/home/tiny/Desktop/job.patch
       apply .patch go particular project right click in eclipse and
                    - > team --> apply patch --> select.patch file

Commit :

      $ > bzr commit -m '[IMP]hr_recruitment improve tooltips

How to push ?
     $ >  bzr push -d addons/trunk-hr_improvements-sbh-recruiment-pna lp:~openerp-commiter/openobject-addons/trunk-hr_improvements-sbh-recruiment-pna

Thursday, 10 May 2012

How to work on Launchpad

How to work on Launchpad :::

Steps :

1. Create your new account in Launchpad

2. To get code

3. who is login?
tiny@tiny:~$ bzr whoami
Pinakin Nayi (OpenERP) <>

4. Get code (get the all changes till now)
tiny@tiny:~$ bzr branch lp:openerp-tools
Branched 181 revision(s).
5. to setup your development environment and download the sources, type
tiny@tiny:~/Desktop/openerp-tools$ sh
- for OpenERP v6.0: make init-v60
- for OpenERP v6.1: make init-v61
- for OpenERP trunk: make init-trunk
- for OpenERP latest stable and trunk: make init

6. Download all branch code
tiny@tiny:~/Desktop/openerp-tools$ make init
init init-repos init-stable init-trunk init-v60 init-v61
tiny@tiny:~/Desktop/openerp-tools$ make init
[ -d addons/6.1 ] || bzr branch lp:~openerp/openobject-addons/6.1 addons/6.1
How to get bug branch ????

1. Suppose you want to push your addons:
cd addons
bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME

2. bzr pull # Get modifications on your branch from others
bzr ci # commit your changes on your public branch

3. If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your
bzr ci --fixes=lp:453123 # Where 453123 is a bug ID

4. than run the server
      $ cd /openerp-tools/server/trunk
      $ ./openerp-server --addons=../../addons/trunk,../../web/trunk/addons/
      how to run GTK client ????
            tiny@tiny:~/Desktop/openerp-tools/client/trunk/bin$ ./

Wednesday, 2 May 2012

Guide to using LaunchPad for OpenERP

Guide to using LaunchPad for OpenERP development

                                                                                     Pinakin Nayi
                                                                                     Trainee at OpenERP India.
                                                                                     Info-City, Gandhinagar.
  1. Create an account for yourself on LaunchPad.
  2. Upload your ssh signature as per
  3. Log in to Launchpad: On Centos:
    bzr launchpad-login <your-launchpad-login>
    On Ubuntu:
    bzr whoami <your-launchpad-login>
  4. Get the latest trunk source code: For the server:
    bzr branch lp:~openerp/openobject-server/trunk
    For the modules:
    bzr branch lp:openobject-addons
  5. To update (cf. svn update, i.e. freshen) your branch later:
    bzr pull

    How to contribute your changes to the OpenERP Community

    1. Join the OpenERP Community here:
    2. You should probably create a bug or mod with a Blueprint on Launchpad in the appropriate project.
    3. Make your changes.
      vi addons/account/
    4. Commit to your local branch.
      cd addons
      bzr ci -m "Testing Modifications"
    5. Push your changes up to Launchpad.
      cd addons
      bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
      Don’t forget to set the status of your branch (new, experimental, development, mature, …) so that contributors know what they can use or not.
    6. Bind your local branch to the one on Launchpad so that future commits will be applied directly to the one on Launchpad.
      bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
    7. Further editing would then follow these steps:
      bzr pull    # Get modifications on your branch from others
      bzr ci    # commit your changes on your public branch
      bzr ci --fixes=lp:453123   # Where 453123 is a bug ID
    8. Update your branch from its parent branch:
      bzr merge
    9. Once your branch is mature, mark it as mature in the web interface of launchpad and request for merging in the official release. Your branch will be reviewed by a commiter and then the quality team to be merged in the official release.