Changes between Version 4 and Version 5 of Development_Workflow


Ignore:
Timestamp:
Sep 2, 2017, 7:00:53 AM (4 years ago)
Author:
Kevin Reed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Development_Workflow

    v4 v5  
    1111
    1212= 1. Proposed Changes = #DevelopmentWorkflowv2-1.ProposedChanges
    13 Code changes should be created because somebody has a problem that cannot be solved with the current version of this software. This could be because the software is doing something wrong (a bug report) or this could be because the software does not yet do something that somebody needs it to do (feature request).
     13Code changes are made because somebody has a problem that cannot be solved with the current version of this software. This could be because the software is doing something wrong (a bug report) or this could be because the software does not yet do something that somebody needs it to do (feature request).
    1414
    1515These changes are documented using [https://github.com/BOINC/boinc/issues issues] on github. A good issue will clearly define the problem that needs to be solved and how the software is not currently solving that problem. In the case of a bug report, this will include instructions on how to reproduce the issue. In the case of a feature request, it will detail the capabilities that are required in order to solve the stated problem.
     
    4040
    4141= 2. Implementation = #DevelopmentWorkflowv2-2.Implementation
    42 All 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.
     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.