Commiting in Launchpad: Guidelines

Hello,

This message is for all Open ERP contributors, to depict our new policy in terms of commit and bugfixes into Launchpad. As you are directly concerned, read carefully the following 4 points and don't hesitate to give feedback!

1. The stable branch must be used for bugfixes only. The new features (+the bugfixes on these new functionalities) have to be done in the trunk branch. Note that, we will backport periodically all the fixes from stable to trunk.


2. Always set the author's name, if it's different from the person who has committed. I heard that some contributors have seen their work has been commited without mentioning their name in the commit message: this is not acceptable at all.

We have to show respect for them and for their work, so please use --author="<author_name>" when merging work or patching features from community.

e.g: bzr commit --author="<author_name>"


3. Format to commit message :

* Use header in each commit message. Header should be out of these: [IMP], [FIX], [REF], [ADD], [REM]

[IMP] : For improvements

[FIX] : For bug fixes

[REF] : For refactoring (improvements of the source code, without changing the functionalities or behaviours. See http://en.wikipedia.org/wiki/Refactoring for further details)

[ADD] : For adding new resources

[REM] : For removing of resources


* Always put meaning full commit message.
Commit message should be self explanatory (long enough) including the name of the module that has been changed. Do not use single words like "bugfix" or "improvements" any-more! (the only single word to commit message accepted is "merge")

* If you are fixing the bugs use --fixes=lp:<bug_number> instead of putting the number of the bug in the commit message.

* Use the revision id instead of the revision number when you make reference to a revision in your commited message. You can get this revision id, by using the command "bzr version-info".

e.g:

Not Correct : bzr commit -m “[FIX]: reverted bad revision (cannot install new db) with revision number:525425”

Correct : bzr commit -m “[FIX]: reverted bad revision (cannot install new db) with revision number id: qdp@tinyerp.com-20090602143202-ehmntlift166mrnn”

Not Correct : bzr commit -m "Bug 568889 : typo corrected"

Correct : bzr commit --fixes=lp:568889 -m "[FIX] account module: typo corrected"


4. Don't make commit which simultaneously impacts lots of modules. Try to splits into different commits where impacted modules are different (It will be helpful when we are going to revert that module separately).


Thanks & Regards,

Open ERP

IRC Community Meeting on 18 May 09

Hello Everybody,

We remind you the next IRC meeting of this Monday May 18 at 3:00 PM (GMT+2), we suggest you to take note of the points which we will approach during this event:

1. Branch stability

2. Installation of an integration server

3. Creation of a forum which talking about the specifics developments

4. Creation of a virtual machine intended to help the new users to start with open erp

5. Contribution to edition of data demonstrations

6. Call to volunteers to enrich the data of openerptv

7. Road map: Talking about the last and future developments

Here thus the principal points which will be approached, but all new topics of discussions are welcome ( http://openobject.com/forum/topic11012.html)!!

Thanks and Best regards,

Open ERP team

OpenERP forum with RSS / Atom feed

Now enjoy the extension of our OpenERP Forum with RSS / Atom feed.

You can choose your favorite discussion / topic on Forum and mark as RSS to get on your desired place.

Or you can choose “Atom” from URL of the page from address bar.

After click on RSS / Atom link, you will get a view like…

So, get updated with Forum as and when you wish, on your demand.