Page History

...

The contribution workflow for small features/bug fixes and and large features.

Small Features / Bug Fixes

...

For large features usually multiple people need to collaborate on a separate branch. Here is where git shines and the distributed model kicks in:
1. A JIRA is created for a large feature.
2. The team (not necessarily having a committer) creates a remote repository which itself may have many branches with the master branch having all the work agreed upon and merged (actually, rebased)
3. The collaboration for this branch happens in the JIRA including discussions, comments, and even links to the commits, etc ...
4. A request is made to the project, to make a pull request from the repository after reaching a certain milestone with consensus from the community of course.
5. Here, for extra safety, the branch model may have a trunk and a develop branches. Everything is pulled to the develop branch and trickles down to the master branch after thorough and proper testing.

The above workflow can also adhere to the now famous Vincent Driessen git branching model found here -> http://nvie.com/posts/a-successful-git-branching-model/

...

•  We should make sure the buildbots are enables enabled on the commits for the above mentioned repository.
  

...

Release management

We will have a branch for the release management, currently we have three branches in https://github.com/apache/ofbiz-framework/

...

In OFBiz, we cut a release and thoroughly test it and then finally make it available to the public.

To create a new release, a branch will be cut from the trunk.

Ideally, the branch will be cut from the trunk branch. So make sure you are on the trunk branch.
Here is the example, we have cut the release19.06.

...

As mentioned by Unknown User (jleroux), we should have an equivalent of svn:auto-props properties on the server.
Something we will need to not forget when we will switch to Git: https://help.github.com/articles/dealing-with-line-endings/#per-repository-settings

Update the website, wiki documents, and references

After the successful migration to Git, we should update this information to various resources like website, wiki documents, and references.

•  Update the information related to Git on OFBiz website Unknown User (swapnilmmane)
  https://ofbiz.apache.org/source-repositories.html
  
•  Update the information related to Git to OFBiz tutorials Unknown User (swapnilmmane)
  OFBiz Tutorial - A Beginners Development Guide

...