#githu

AG Githu Muigai asks MPs to extend gender rule deadline by one year

By CAROLINE WAFULA More by this Author

The Attorney-General has asked Parliament to extend for one year the deadline for legislation to implement the one-third gender rule.

Prof Githu Muigai’s advice will be a blow to women MPs and gender activists who have been lobbying to have the rule implemented as per the Supreme Court ruling.

The gender rule is meant to increase the representation of…

We (@mifos) use Github service as revision control system. And above diagram shows the infrastructure setup. Even though we use a distributed version control workflow, we use openMF account as central copy (symbolic) only for release management activity.

OpenMF: Is our organizational Github account and openmf/mifosx is used as symbolic centralized repository for release management, also act as upstream repo.

Steve: is Steve’s github account (username), it is recommended for each contributor to open account in Github and  fork the repo rather than directly requesting for pull (request-pull). Also use forked repo as origin repo. (Act as backup till your pull requested is accepted and provide more visible/open collaboration on each pull request with project maintainer about code review/feedback).

Our git workflow defines a strict branching model designed around the project release. This workflow assigns very specific roles to different branches and defines how and when they should interact. In addition to feature branches, it uses individual branches for preparing, maintaining, and recording releases. Of course, you also get to leverage all the benefits like pull requests, isolated experiments, and more efficient collaboration.

How It Works

Our workflow uses a central repository as the communication hub for all developers. And developers work locally and push branches to the origin repo and from origin repo make request for pull.

Instead of a single master branch, this workflow uses two branches to record the history of the project. The release specific branch stores the official release history, and the develop branch serves as an integration branch for features. It's also convenient to tag all commits in the master branch with a version number.

Release Branches

Each new release should reside in its own branch, which branched off of master. But, instead of branching off of master, feature branches use develop as their parent branch. When a feature is complete, it gets merged back into develop. Features should never interact directly with master.

Once develop has acquired enough features for a release (or a predetermined release date is approaching), no new features can be added to develop after this point—only bug fixes, documentation generation, and other release-oriented tasks should go in develop.

Once it's ready to ship, you merge develop into master and a release branch off of master with version number. Creating this branch means product is released,

Hotfix branches

Hotfix branches are used to quickly patch production releases. This is the only branch that should fork directly off of release branch. As soon as the fix is complete, it should be merged into both master and develop.

Having a dedicated line of development for bug fixes lets our team address issues without interrupting the rest of the workflow or waiting for the next release cycle. You can think of maintenance branches as ad hoc release branches that work directly with release branch.

One of the drawback of this approach is

1) Once develop is ready for release, no more pull-requests are accepted and we are some what blocking development on develop branch. But main idea behind develop branch is to have  continuous development stream.

Other side we have an advantage of this model is for volunteers without much aware of release plans they can contribute and project maintainer can take care of cherry picking it to a bug fix branch if required

External links

https://www.atlassian.com/git/workflows#!workflow-gitflow

http://nvie.com/posts/a-successful-git-branching-model/

Githu: ICC wants to freeze Uhuru’s assets

Prosecutor Fatou Bensouda’s request for President Uhuru Kenyatta’s property records is a ploy to “freeze and seize” his assets, according to the attorney-general.

Prof Githu Muigai accused the prosecution of using the revised request to go back to the suspended pre-trial chamber’s order for “identification; tracing and freezing or seizure” of property and assets of Francis Muthaura, Mr…