Page History

...

How should committers handle backporting?

1. Only bugfixes should be backported to active release branches (if they happen also there).
2. Bugfixes should be backported by the committer who did the bugfix in trunk, if possible.
3. If the committer does not, for an reason, backport the bugfix, he should leave the original issue open with a remark that a backport is needed and a short explanation why he does not do the backport.
4. Issues which need a back port should be labelled as "back port-needed". In this way we are able to spot issues to be backported, especially before a release is on it's way. 
5. In no case should the Jira issue be closed without doing 1. or 2.
6. When you backport something, if you know that it should not be backported in older releases, please pass the information.

Christian Carlow asked

Should committers download the entire ofbiz repository to help with backporting?

...

ofbiz/
ofbiz/trunk
ofbiz/release14.12
ofbiz/release13.07
ofbiz/release12.04
ofbiz/site

Is there a standard procedure new committers should follow for backporting?

Only bugs should be backported to active release branches (if they happen also there); it is not mandatory that you do but it is very much appreciated! Here is a simple workflow to backport a commit to a branch. 

1) commit the fix to trunk and note down the commit id; e.g. rev 12345
2) go to the release branch you want to backport to; e.g. cd ofbiz/release14.12
3) run the following script (the script will apply the commit to your local release branch): ./tools/mergefromtrunk.sh/bat merge 12345
4) run the tests with: ./tools/mergefromtrunk.sh/bat test
5) it is also a good idea to start the instance and test manually
6.a) if tests are unsuccessful, abort the process and clean your local release branch: ./tools/mergefromtrunk.sh/bat abort
6.b) if tests are successful, and you want to commit the backport: ./tools/mergefromtrunk.sh/bat commit

...

 commit

Following changes

Manage JIRA's issues

...

• Road Map (what is expected in upcoming releases) : https://issues.apache.org/jira/browse/OFBIZ/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel

• Change Log (what is available in released packages available from the Download page) : https://issues.apache.org/jira/browse/OFBIZ/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel

  Note
  title Reminder
  If the svn commits comments are correctly done, with a reference to the Jira issue number, we can then get to the commits in Fisheye from the Development section of the Jira issue. These can take a few days though... Also, please put the revision number in the Jira issue. That helps others doing research on changes.

• Note about backports for bug fixes

...

• .

...

Complete the documentation

...