forked from calagator/calagator
-
Notifications
You must be signed in to change notification settings - Fork 0
ContributingIncompleteCode
Reid Beels edited this page Aug 4, 2011
·
1 revision
How to contribute code that is incomplete
**Labels:**Deprecated
- If you think you can finish a project during the code sprint, then work from the trunk.
Otherwise: Put the code in a branch, and WIKI PARSE WARNING: unterminated '*'! Add an [http://code.google.com/p/calagator/issues/list Issue] so that the branch isn't forgotten. WIKI PARSE WARNING: unterminated '*'! (Ideally all incomplete pieces of code in the branch are flagged so someone else can complete the project if they have time).
Sometimes (despite your intentions) when you work from the trunk, the code turns out to be less finished than you'd like, or it breaks part of the application. Here's how that code should be handled:
==1st choice==
- Comment out the code (so that we don't lose all the work). and
- Flag it with an Issue.
==2nd choice== If it's not possible to comment out and flag the code, then
- selectively roll back the changes,
- cherry pick and keep the good ones,
- put the other (not good) changes into a branch, and
- flag the branch with an Issue.