Changes between Version 3 and Version 4 of Development_Workflow


Ignore:
Timestamp:
Sep 1, 2017, 2:54:25 PM (4 years ago)
Author:
Kevin Reed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Development_Workflow

    v3 v4  
    1 = Development Workflow  =
     1= Development Workflow =
    22The purpose of a development workflow is to make sure that the BOINC platform produces high quality code that solves the problems of its users. As such, the development workflow needs to have checkpoints to allow for the review and discussion of the following questions:
    33
     
    4040
    4141= 2. Implementation = #DevelopmentWorkflowv2-2.Implementation
    42 All development is done using feature branches. Review [https://guides.github.com/introduction/flow/ GitHub Flow]. BOINC uses the [https://gist.github.com/Chaser324/ce0505fbed06b947d962 Fork and Pull Model] for development (background on this approach can be [https://help.github.com/categories/collaborating-with-issues-and-pull-requests/ read here]). Once you have created your fork, set it up locally, and created a feature branch, you can begin coding. When you are finished with development you can create a pull request for review.
     42All development is done using feature branches as defined in [https://guides.github.com/introduction/flow/ GitHub Flow]. BOINC uses the [https://gist.github.com/Chaser324/ce0505fbed06b947d962 Fork and Pull Model] for development (background on this approach can be [https://help.github.com/categories/collaborating-with-issues-and-pull-requests/ read here]). Once you have created your fork, set it up locally, and created a feature branch, then you can begin coding. When you are finished with development you can create a pull request for review.
    4343
    4444Make sure to review the [wiki:Definition_of_Done_for_Feature_Branches] before starting work so that you are familiar with the expectations of your work.