Skip to content
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.

Mifos X Committer Guidelines

Vishwas Babu A J edited this page Jul 31, 2014 · 1 revision

Merge Process

  1. Ensure that the pull requests adheres to our coding standards and pre-requisites listed at https://github.com/openMF/mifosx/blob/develop/Contributing.md
  2. Do not bring in any in-progress / incomplete work into the main branches (develop, bug-fix) of any openmf repository
  3. Upon Bringing in any work to a develop or Bug fix branch, change the status of the issue on Jira to "Ready for testing" and assign the same to our dedicated QA resource ([email protected])

Release process

Stable Release

All pull requests are sent to the develop branch. We try to ensure that at any given point in time the develop branch is release ready (we currently ship atleast one release every month, release details can be found at https://mifosforge.jira.com/secure/RapidBoard.jspa?rapidView=2&view=planning&selectedIssue=MIFOSX-773&versions=visible&selectedVersion=14530)

Bug Fix Release

Guidelines for the new Committer

  • Never force a push to an openMF repository (unless you are 100% sure of what you are doing!)
  • Do not commit you changes directly to the openMF repository. Follow the pull request model, let another committer review and merge your work