-
Notifications
You must be signed in to change notification settings - Fork 6
Home
amcgee edited this page Oct 31, 2014
·
19 revisions
(NOTE: The Wiki has been deprecated in favor of the documentation page at welldone.github.io/MoMo-Firmware. If the documentation site is missing any information on the wiki, it should be added to the repository in the doc directory.)
This is the canonical home of working design decisions for the MoMo device firmware. To get started quickly, read Getting-Started
Check out the tutorials page to get up to speed with how to use the MoMo system.
##Version 1.0 Roadmap MoMo is on the path to 1.0. The roadmap of features that need to be implemented before 1.0 is here.
-
Master
is for production-ready code ONLY. - Released versions are tagged on the
Master
branch -
Dev
should be considered HEAD. It is the most cutting-edge stuff that is still relatively stable. - Developer branches should be kept locally, not pushed to GitHub.
- Patches and major releases can be developed in parallel on separate branches following the naming patter
release-0.1
orpatch-1.3
. Only bug fixes should be directly committed to these branches. - Major features should have their own branches (named anything not beginning with
release-
orpatch-
), allowing peripheral developer cooperation. - When a release, patch, or feature is complete and has been merged back into
dev
andMaster
, the corresponding branch should be deleted. -
ALWAYS merge with the no fast-forward option -
git merge --no-ff <source_branch>
. Life is just better that way.
These rules were inspired by the conventions outlined here. Respect.