Changes between Version 3 and Version 4 of Development_Workflow

Timestamp:

Sep 1, 2017, 2:54:25 PM (7 years ago)

Author:

Kevin Reed

Comment:

--

Development_Workflow

@@ -1 @@
-= Development Workflow  =
+= Development Workflow =
 The 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:
 
@@ -40 +40 @@
 
 = 2. Implementation = #DevelopmentWorkflowv2-2.Implementation
-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.
+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.
 
 Make 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.