ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Contribution workflow (Task #18)

Added by Muntek Singh at 2010-12-29 10:38 am. Updated at 2011-02-01 07:24 am.

Status:Closed Start date:2010-12-29
Priority:Normal Due date:
Assignee:Holger Just % Done:

50%
Category:ChiliProject - Organization
Target version:Public Launch
Remote issue URL:

Description

Setup a contribution workflow based on git - including code review process

History

#1
Updated by Muntek Singh at 2010-12-29 10:39 am

Should create two wiki pages:

Broad overview of how bluemine code contributions work

How bluemine does code review

#2
Updated by Eric Davis at 2011-01-04 03:02 pm

I started on a basic Contribute page and am working on a Code Review one now. I think this is good enough to launch, we will be changing these as we refine the development process.

  • Assignee set to Eric Davis

#3
Updated by Eric Davis at 2011-01-04 03:24 pm

I've done a brain dump of my own Code Review system to the wiki. Still need to create the actual process but I think these don't need to be finalized before we launch.

  • % Done changed from 0 to 50
  • Status set to In Progress

#4
Updated by Eric Davis at 2011-01-12 01:56 pm

  • Project changed from Organization to ChiliProject
  • Target version deleted ()
  • Category deleted ()

#5
Updated by Eric Davis at 2011-01-12 01:58 pm

  • Category set to ChiliProject - Organization

#6
Updated by Eric Davis at 2011-01-12 02:29 pm

  • Tracker changed from Feature to Task

#7
Updated by Eric Davis at 2011-01-12 03:11 pm

  • Target version set to Public Launch

#8
Updated by Felix Schäfer at 2011-01-21 05:21 pm

Proposed workflow: http://nvie.com/posts/a-successful-git-branching-model/, though we should probably rename the "master" branch from the post to "stable" and the "develop" branch to "master", as the "master" branch commonly is the branch development happens on on github.

#9
Updated by Felix Schäfer at 2011-01-21 11:42 pm

Contribute will probably need some smaller adjustments, but should be mostly OK, the code part has been moved to Contribute Code and needs work still.

#10
Updated by Felix Schäfer at 2011-01-24 12:59 pm

I think Contribute Code is at a point I'd call it finished save for smaller wording/grammar fixes. I've begun on the Branch names and general "code flow" on Release Process, you might want to have a look there too.

#11
Updated by Felix Schäfer at 2011-01-27 02:47 pm

Contribute Code is finished, the branch names are now on ChiliProject Repository, they should be finished once we have a graphic to show it all (Holger's on that currently).

Once the Code Review is deemed finished, this can be closed.

#12
Updated by Eric Davis at 2011-01-27 10:39 pm

Felix,

The wiki pages look good. I think once we have a graphic of the branches we can finish this issue. Code Review can be finished up as we go, it's a more fluid process.

Assigning to Holger for the branch graphic. I can try to create it if needed.

  • Assignee changed from Eric Davis to Holger Just

#13
Updated by Eric Davis at 2011-02-01 07:24 am

Holger added the branch graphic to ChiliProject Repository so this issue is complete.

  • Status changed from In Progress to Closed

Also available in: Atom PDF