THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The history is also the main source for our development report as part of the monthly Apache OFBiz blog. To put it together more efficienlty, we'll try to automate the process and a unified format will support this process very well.
Committers (and other contributors who use Git) should use the following template for their commit messages: (note that with
Jira | ||||||
---|---|---|---|---|---|---|
|
Tip | ||
---|---|---|
| ||
[Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira title | Free text] |
...
- line 1:
- is mandatory, the following lines are optional.
- a ":" follows after the kind of implementation/source of work.
- the Jira title or any other text must not be quoted ("").
- the Jira reference , separated by a new line, is written in parenthesis, no whitespace. It's possible to group several JIRA references together, if applicable. JIRA references are optional (in case there is no Jira).
- no separators between the lines, just new lines.
- remarks regarding the patch (e.g. modifications) and the issue itself are described in the details.
- the optional details are separated by blank lines before and after.
- the line length should not exceed 80 characters.
...
Info | ||
---|---|---|
| ||
Improved: Clean up commented out code in XML for Common component. |
...
Info | ||
---|---|---|
| ||
Improved: Consistent menu names (OFBIZ-8124)(OFBIZ-8125)(OFBIZ-8126) |
...