Software Development Procedure
Last updated
Last updated
For quite a while, I have been participating in the ADempiere project as a committer. Throughout this time the group of developers has experienced the increasing complexity of managing this project as a mission-critical software development endeavour.
This process has been occasionally not only complex but also tedious, since the philosophy of our project is based on the Bazaar approach, that expects many contributors with different profiles, experience and ways of thinking. So the big question is: how to manage the project with all these contributors?
On the one hand we have contributors (aka committers) with great experience in the project. They want to and often do contribute with new features, generating a dynamic line of development. Many of these new features can be brought to our committee for approval and inclusion in the main develop branch.
This process is very important because it lets us review and evaluate new features by experts both technical and functional.
Another important aspect is the incredible ability of contributors to create new features, usually beginning with a creative idea that evolves and matures. After this has happened, the contributor wishes to show his deeds to others to receive feedback and eventually to submit for trial.
The new features can be fully completed or in progress, but it is important to establish a policy of sharing functionality in order to evaluate the pros and cons of the feature.
The process nowadays is complex because there aren't tools and procedures enabling dynamic collaboration. As a consequence of that, the project may be or seem to be stalled or still worse, these new features are never included within the main trunk, limiting the creativity and innovation of the project.
On the other hand there are contributors who discover a problem/bug in the program. They create a solution to the problem in their private repository. In many cases, many of these bug fixes do not land in the main line of code.
Why? In my opinion, it is because of the lack of tools and of a process that explains how to share, how to facilitate collaboration, reviews and evaluation of bug fixes in a simple way.
Another aspect of our software development concerns the release of new versions that include bug fixes as well as new features are approved by the project committees. In the current approach, the main line of code must be frozen during the release process. This simplifies the process for the technical equipment, but has the disadvantage of stopping the momentum of a Bazaar-like project like ours, which is in constant evolution.
The release process also involves steps towards maintaining already released versions. These versions are not fault-free and so it is possible to find errors anew. Thus the versioning process is an additional task for the technical team, and using a tool to facilitate the creation of a service pack becomes a key factor.
Once the major issues were pinpointed, the technical committee analyzed and improved the current development process. As a result of this, changes were made in the current procedure in order to solve the current problems and thus improve collaboration in the project.
Kind regards
Member of Technical Team
This document is about establishing processes, rules and teams to achieve the following:
Produce high quality ERP software
Regular and schedule releases
An all the time stable “master” branch
Explicit and concise rules how to manage the ADempiere Code Repository
Reduce overhead caused by reverts for unfinished features
Documentation for all new features
Teams are to be responsible not single persons
Lean project organisation
Continuous and reliable progress
Increase collaboration among developers
Facilitate the task of project management
Here, a couple of important definitions are introduced shortly to help the understanding of the processes, but explained in detail below:
Main branch
master Branch (before: stable)
Only for release and hotfixes approved
An infinite lifetime
develop Branch (before: development)
Main line of code
An infinite lifetime
Never freezes.
Gets voted and approved commits from features branches.
No experiments
Support Branches (before directly in trunk)
Release
Feature
Hot Fixes
These branches always have a limited life time
Since they will be removed eventually.
Development Phase (3 Months)
“develop” branch which is the main line of development.
New functionalities are implemented in separate “feature” branches with the aim to get them into develop branch
Developers have 3 months time for integrating new functionalities, changes, Bug fixing and Integration testing in their branch
Before integrating new/ changed Functionality in "develop" the Developers/ Implementers have to apply for approval by Technical and Functional Team
Stabilization Phase (1 month)
After development phase is over there is one month stabilization phase where the “release” branch is created and frozen for new features. In this time only bug fixing and User Acceptance Tests (UAT) are allowed.
Release
When “release” branch is finished, it is integrated back into the develop and master branches, which are the main line of development. Eventually, a release is done using a tag.
The next stabilization branch cycle starts. The old branch is close.
Responsibilities
Code is formatted using the official formatting definition (need to be defined and agreed on, but in meantime you can take this as an example)
Announce any data model change in order to discuss and vote it in Technical and/or Functional team (example: the placed were we store some well known data like contact phone changed)
Announce structural changes (e.g. file, directory, rename, move, delete) should be announced and approved by Technical team before applying it
Keep Master Data Models (organizations, business partners, contacts, warehouses etc) consistent and do not use different ways of defining the relations between this entities (examples: storing the organization details like addresses, phones, faxes in Organization Info tab or in the linked business partner)
In case of complex functionalities, define ADempiere Generic Workflows in order to guide the user how to setup the functionality and which is the designed the business process (example: take a look at Manufacturing Management Setup workflow from your ADempiere main menu)
Provide necessary documentation:
Forum post announcing the development in forum
Wiki page (template and content to be defined)
Feature request in tracker
Entry in Feature Development Collaboration wiki page
Keep his/her branch up-to-date with “master” branch and therefore must merge hotfixes into his/her branch.
Provide immediate effort if the integration harms the "master" branch.
Delete "dead" or "unmaintained" branches created in the past.
Process
In summary:
Developers should have their own account on GitHub.
Working on their local clone, developers can open a new “feature” branch or contribute to any other branch using the Gitflow Workflow' model.
To have their work merged into the main repository, developers issue a pull request from their GitHub account. This will initiate a discussion with other developers, leading to the inclusion of the new work.
Calculate 4 hours minimum work per week
Responsibilities
Maintains “master” and “develop” branch
Ensures that all contributions meet technical requirements in respect to quality:
Code is well documented
Backward compatibility is achieved
Migration scripts complete
technical documentation sufficient
backward comparability analysis
migration scripts are provided (when needed)
Regular releases by providing and supporting a release manager from amongst their members
Note: More detail in main branches section
Process
When a contribution (either a bug fix or new feature) is ready for approval the developer submits a Pull Request on GitHub
Technical Team meets on a regular basis and discusses the Pull Requests. The team and other developers can collaborate on the pull request if required.
If all criteria are met the team approves the feature from a technical perspective
The Maintainer merges the pull request into the main repository.
Note: More detail in features branches section
Actual Staff (since March 2016)
Victor Pérez
Mario Calderón
Yamel Senih
Gabriel Vila
Mike McKay
Release Manager
Responsibilities
Organize contributions to keep release schedule
Maintains release tags
Integrate new release branch to master branch
Process
Creates “release” branch from “develop” branch when new development cycle begins
Produces a release from “develop” branch after stabilization phase
Creates tags and merge change set into the “develop” and “master” branches
Note: More detail in release branches section
Calculate 4 hours minimum work per week
Responsibilities
Ensures that all contributions meet functional requirements in respect to quality
Requirement is reasonable
Feature is needed in “develop” branch or to be kept as optional extension**
Requirement is solved
Acceptance criteria are defined
Test cases are complete
User documentation is sufficient
System documentation is sufficient
Process
The Functional team has got the final decision on which feature is accepted and merged from “feature” branch to “develop” branch.
Actual Staff (since March 2016)
Mike McKay
Jatinder Kansal
Victor Pérez
Mario Calderón
Eduardo López
Yamel Senih
Gabriel Vila
Enrique Ruibal
Colin Rooney
Michael Judd
There are already other teams that could be integrated into this Integration Process where it makes sense. For example Usability, Security team.
In exception to the Software Production Cycle there is also the possibility to apply hotfixes
Technical and functional team can approve that hotfixes go directly to “master” branch and “development” branches
Note: More detail in Hotfix branches section
The Technical Team agreed to maintain only one Service Pack of a former version. It would be great to support for several years (typical for this kind of applications) but our community’s resources are scarce.
A Service Pack can be obtained by comparing the tag of the released version with the last changeset applied by a hotfix from the master branch. This process can be automated via a script that makes a compare and generates a patches.jar which will be applicable to the last version.
Technical team has the responsibility to revert code that has been committed without approval
The revert should be motivated precisely and without any doubt.
Any other person outside of the technical team (including the functional team) is not allowed to revert, but is advised to call for a revert by specifying the concrete reasons.
The revert procedure will use the repository facility that allows posts history and the reason of the revert, so a change set or commit are necessary to execute the revert.
In order to approve a contribution at least 2/3 of team members need to vote positively
Everybody can become a member of one of the teams
The team can expel a member when one of the following applies
member does not show up for three meetings without informing the other members in advance
2/3 of the team vote for expelling the member
As there might be changes to the version control software (e.g. switching to mercurial, git) technical terms (e.g. trunk) or best practices might become obsolete. In this case the teams can advance this concept and adapt it to needs of the future. The same applies for duration of cycles that might become a subject to change.
The only thing that the teams are not allowed to change and that is hereby voted and enforced by the citizens is
Features need always approval before they hit the main line of development to avoid excessively number of reverts => Goals "reduce overhead caused by reverts for unfinished features" and "clear rules how to get repository code "
The aim should always be high quality of the software. If a feature is putting the quality of the adempiere to risk it should not be approved. => Goals "produce high quality ERP software" and "an all the time stable version"
New features need to be applied with documentation for users and developers => Goal "documentation for all new features"
The power to take decisions and organizing processes should be with teams and not single persons. => Goals "teams are to be responsible not single persons" and "lean project organisation"
Team members need to dedicate a minimum amount of hours per week to the work. They need to agree on that before they become part of the team. => Goal "continuous and reliable progress"
If all of above is applied we will have "regular and schedule releases".
master
develop
The master branch at origin should be familiar to every developer. Parallel to the master branch, another branch exists called develop.
We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state.
We consider origin/develop to be the main branch where the source code of HEAD always reflects a state with the latest delivered develop changes for the next release. Some would call this the “integration branch”. This is where any automatic nightly builds are built from.
When the source code in the develop branch reaches a stable point and is ready to be released, all of the changes should be merged back into master somehow and then tagged with a release number. How this is done in detail will be discussed further on.
Therefore, each time when changes are merged back into master, this is a new production release by definition. We tend to be very strict at this, so that theoretically, we could use a script to automatically build and roll-out our software to our production servers everytime there was a commit on master.
Next to the main branches master and develop, our development model uses a variety of supporting branches to aid parallel development between team members, ease tracking of features, prepare for production releases and to assist in quickly fixing live production problems. Unlike the main branches, these branches always have a limited life time, since they will be removed eventually. The different types of branches we may use are:
Feature branches
Release branches
Hotfix branches
Each of these branches have a specific purpose and are bound to strict rules as to which branches may be their originating branch and which branches must be their merge targets. We will walk through them in a minute.
By no means are these branches “special” from a technical perspective. The branch types are categorized by how we use them. They are of course plain old Mercurial branches.
May branch off from: develop
Must merge back into: develop
Branch naming convention: anything except master, develop,release-*, or hotfix-*
Feature branches (or sometimes called topic branches) are used to development new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into develop (to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment).
Feature branches typically exist in developer repository only, not in origin.
Creating a feature branch
When starting work on a new feature, branch off from the develop branch.
Incorporating a finished feature on develop
Finished features may be merged into the develop branch definitely add them to the upcoming release.
May branch off from: develop
Must merge back into: develop and master'
Branch naming convention: release-*
Release branches support preparation of a new production release. They allow for last-minute dotting of i’s and crossing t’s. Furthermore, they allow for minor bug fixes and preparing meta-data for a release (version number, build dates, etc.). By doing all of this work on a release branch, the development branch is cleared to receive features for the next big release.
The key moment to branch off a new release branch from develop is when development (almost) reflects the desired state of the new release. At least all features that are targeted for the release-to-be-built must be merged in to develop at this point in time. All features targeted at future releases may not—they must wait until after the release branch is branched off.
It is exactly at the start of a release branch that the upcoming release gets assigned a version number—not any earlier. Up until that moment, the development branch reflected changes for the “next release”, but it is unclear whether that “next release” will eventually become 3.6 or 4.0, until the release branch is started. That decision is made on the start of the release branch and is carried out by the project’s rules on version number bumping.
Creating a release branch
Release branches are created from the develop branch. For example, say version 1.1.5 is the current production release and we have a big release coming up. The state of develop is ready for the “next release” and we have decided that this will become version 1.2 (rather than 1.1.6 or 2.0). So we branch off and give the release branch a name reflecting the new version number.
After creating a new branch and switching to it, we bump the version number. Here, bump-version.sh is a fictional shell script that changes some files in the working copy to reflect the new version. (This can of course be a manual change—the point being that some files change.) Then, the bumped version number is committed.
This new branch may exist there for a while, until the release may be rolled out definitely. During that time, bug fixes may be applied in this branch (rather than on the develop branch). Adding large new features here is strictly prohibited. They must be merged into develop, and therefore, wait for the next big release.
Finishing a release branch
When the state of the release branch is ready to become a real release, some actions need to be carried out. First, the release branch is merged into master (since every commit on master is a new release by definition, remember). Next, that commit on master must be tagged for easy future reference to this historical version. Finally, the changes made on the release branch need to be merged back into development, so that future releases also contain these bug fixes.
Now we are really done and the release branch may be removed, since we don’t need it anymore:
May branch off from: master
Must merge back into: develop and master
Branch naming convention: hotfix-*
Hotfix branches are very much like release branches in that they are also meant to prepare for a new production release, albeit unplanned. They arise from the necessity to act immediately upon an undesired state of a live production version. When a critical bug in a production version must be resolved immediately, a hotfix branch may be branched off from the corresponding tag on the master branch that marks the production version. The essence is that work of team members (on the development branch) can continue, while another person is preparing a quick production fix.
Creating the hotfix branch
Hotfix branches are created from the master branch. For example, say version 1.2 is the current production release running live and causing troubles due to a severe bug. But changes on develop are yet in process. We may then branch off a hotfix branch and start fixing the problem.
Don’t forget to bump the version number after branching off! Then, fix the bug and commit the fix in one or more separate commits.
Finishing a hotfix branch
When finished, the bugfix needs to be merged back into master, but also needs to be merged back into develop, in order to safeguard that the bugfix is included in the next release as well. This is completely similar to how release branches are finished. First, update master and tag the release.
The one exception to the rule here is that, when a release branch currently exists, the hotfix changes need to be merged into that release branch, instead of 'develop branch.
Back-merging the bugfix into the release branch will eventually result in the bugfix being merged into develop too, when the release branch is finished. (If work in develop immediately requires this bugfix and cannot wait for the release branch to be finished, you may safely merge the bugfix into develop now already as well.)
Finally, remove the temporary branch.
ADempiere is tested by a team of volunteers at each major release.
If you want to fix a bug you can do it two ways
if you are an ADempiere developer, you have tested your code thoroughly and you are sure of what you've done: just do the commit and the push in the corresponding branch after consulting the Technical and Functional Team.
This is described below.
Open a console or terminal.
Create a backup for example with the command cp adempiereSource adempiere.bak
Go to the sources for example with cd adempiereSource
Execute git pull
Execute git checkout hotfix/3.8.0#002. This is because you want the bug fix applies to this very branch. If there is another branch you want the bug fix to be applied, just modify the checkout command accordingly.
Do changes and modifications towards bug fixing in the branch (in our case hotfix/3.8.0#002).
Execute git commit -m 'my comments to the bug fixing, with reference to the altlassian/github site were the bug was created'
Execute git push
For new hotfixes, all patches will be collected and tested, and a collection of all patches (patches.jar) will be created for the branch. contribute.
if you are not an ADempiere developer or you are an ADempiere developer, but you don't want to commit nor push it directly because you want others to check it before committing and pushing:
you must create a branch where you want do the bug fix.
do the modifications there
create a pull request in your branch.
Your pull request can be used in other branches
This is an effective ans easy way of collaboration, where developers and non-developers can contribute.
Assure that code has 100% compliance with
Respect the Distributed Version Control Best Practices (see )
The software development process uses a combination of workflows. For some great background on workflows, see the Atlassian article on
The main repository at is managed using a process similar to the Gitflow Workflow in the Atlassian article. The maintenance of the main repository is the responsibility of the Maintainer.
Developers contributing to the project use the Forking Workflow with the GitHub Fork and Pull model. Refer to the Github article on for details.
The Maintainer manages the main repository (
Developers fork the main repository on GitHub to their personal account ( and make a local clone of their personal fork.
If the developer is working with Jira a lot, they should link their GitHub account with the project Jira account. This requires the help of a Jira administator so ask in the Developers forum. There is a good (if you don't mind elevator music) on youtube showing what is involved.
Developers commit to their local clone and push to their fork using well documented commits. To use the smart commits that link to the Jira issues, follow the . It is important to use the uppercase references (e.g. ADEMPIERE-123) in the commit messages. Read the instructions for more information.
| | Note:While the main repository will be following the branch naming very closely, developers are encouraged to use more descriptive names for their branches and to develop these "tracking" branches from a recent point on the Adempiere (origin) project. The branch should contain only the changes relevant to the pull request and the pull request should target the correct branch on the origin repository. Once the pull request has been accepted and closed the tracking branch can be deleted. (Branches in git are only pointers so deleting the branch tag leaves all the history intact.) | | :--- | :--- |
| | Note:Needs discussion. | | :--- | :--- |
| | Note:Needs discussion. Is it relevant with the new methods? | | :--- | :--- |
| | Note:Needs discussion. | | :--- | :--- |
The central repository holds two main branches with an infinite lifetime:
Automated testing of ADempiere is also performed using test scripts that cover the critical functions. For more information, refer to .
See , and .
In the you can create a pull request for this commit. This pull request can be used in other branches.
