Changes between Version 10 and Version 11 of CollaborateOnGithub

Timestamp:

Jan 17, 2009, 8:11:56 AM (17 years ago)

Author:

mrts

Comment:

--

CollaborateOnGithub

@@ -120 +120 @@
  }}}
  1. When the feature is ready, send the lieutenant a pull request by clicking ''pull request'' on your forked project's page.
+
+== Quality assurance ==
+
+To assure that the contribution is in par with Django code quality standards, the actual development workflow should be similar to the following:
+
+=== Contributor ===
+
+ 1. Implement tests for the features to be added
+ 1. Commit locally with a descriptive commit message
+ 1. Implement the features
+ 1. Commit locally
+ 1. Run the test suite iteratively, fixing whatever the tests indicate needs fixing
+ 1. Commit locally if something changed
+ 1. Push your changes to !GitHub
+
+=== Lieutenant ===
+
+ 1. Review changes (knowing that the contributor has assured that tests pass)
+ 1. Pull changes from contributor's repo to your repo
+ 1. Run the test suite
+ 1. Push changes to the public code hosting service