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

Branching Strategy

Jump to bottom
Steve Maillet edited this page Mar 16, 2015 · 5 revisions

The branching strategy for the .NET Micro Framework is a common form using a master branch for all official releases, hotfix branches for any patches and a dev branch for centralizing future development and individual feature branches for in progress feature work. A more detailed description of the process is available in this excellent article by @nvie. A key difference from the strategy described in the article is due to hosting the central repository on GitHub. Pull Requests on GitHib require a GitHub fork so each individual's "origin" repository is their forked version stored on GitHub. Pull requests are made to the central repository from your fork. Thus there are a few extra steps from what @nvie describes due to how GitHub works but the general principals apply.

  1. Getting Started
    1. Differences from previous CodePlex and the Porting Kit releases
    2. Contributing
    3. Coding Standards
    4. Branching Strategy
    5. Build System Requirements
  2. Architecture of the .NET Micro Framework
    1. Physical hardware
    2. CPU Support layer (CPU)
    3. Hardware Abstraction Layer (HAL)
    4. Operating System (OS)
    5. Platform Abstraction Layer (PAL)
    6. Common Language Runtime (CLR)
    7. Interop
    8. Base Class Libraries
  3. Tools
    1. MetadataProcessor
  4. File Formats
    1. PE Metadata File Format
Clone this wiki locally