From 8bb16ff2bbce53daf43693674ff2801e61458703 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Mon, 19 Feb 2007 05:59:30 +0000 Subject: [PATCH] fix TOC, clarify bullet in incremental dev git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34407 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/DeveloperPolicy.html | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 1bf62f17aab..e3e37f0bc1f 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -24,13 +24,6 @@
  • Attribution of Changes
    • -
  • Patch Policies -
      -
    1. Patch Form
      2. -
    2. Patch Submission
      3. -
    3. After Submission
      4. -
    4. After Commit
      5. -
  • Copyright and License
    1. Copyright
      2. @@ -310,12 +303,15 @@ quality patches. If you would like commit access, please send an email to the
    2. The remaining inter-related work should be decomposed into unrelated sets of changes if possible. Once this is done, define the first increment and get consensus on what the end goal of the change is.
      3. -
    3. Increments can be stand alone (e.g. to fix a bug), or part of a planned - series of increments towards some development goal.
      4. -
    4. Increments should be kept as small as possible. This simplifies your + +
    5. Each change in the set can be stand alone (e.g. to fix a bug), or part + of a planned series of changes that works towards the development goal.
      6. + +
    6. Each change should be kept as small as possible. This simplifies your work (into a logical progression), simplifies code review and reduces the chance that you will get negative feedback on the change. Small increments also facilitate the maintenance of a high quality code base.
      7. +
    7. Often, an independent precursor to a big change is to add a new API and slowly migrate clients to use the new API. Each change to use the new API is often "obvious" and can be committed without review. Once the