diff --git a/src/postorius/doc/_build/doctrees/development.doctree b/src/postorius/doc/_build/doctrees/development.doctree index 5084170..1d6bc19 100644 --- a/src/postorius/doc/_build/doctrees/development.doctree +++ b/src/postorius/doc/_build/doctrees/development.doctree Binary files differ diff --git a/src/postorius/doc/_build/doctrees/environment.pickle b/src/postorius/doc/_build/doctrees/environment.pickle index 5a76bd2..31263b6 100644 --- a/src/postorius/doc/_build/doctrees/environment.pickle +++ b/src/postorius/doc/_build/doctrees/environment.pickle Binary files differ diff --git a/src/postorius/doc/_build/html/_sources/development.txt b/src/postorius/doc/_build/html/_sources/development.txt index b560812..76b5eb1 100644 --- a/src/postorius/doc/_build/html/_sources/development.txt +++ b/src/postorius/doc/_build/html/_sources/development.txt @@ -37,6 +37,31 @@ # class for views based on a single mailing list +Development Workflow +==================== + +The source code is hosted on Launchpad_, which also means that we are using +Bazaar for version control. + +.. _Launchpad: https://launchpad.net + +Changes are usually not made directly in the project's trunk branch, but in +feature-related personal branches, which get reviewed and then merged into +the trunk. + +The ideal workflow would be like this: + +1. File a bug to suggest a new feature or report a bug (or just pick one of + the existing bugs). +2. Create a new branch with your code changes. +3. Make a "merge proposal" to get your code reviewed and merged. + +Launchpad has a nice tour_ which describes all this in detail. + +.. _tour: https://launchpad.net/+tour/index + + + Writing View Code ================= diff --git a/src/postorius/doc/_build/html/development.html b/src/postorius/doc/_build/html/development.html index a1a0494..478112e 100644 --- a/src/postorius/doc/_build/html/development.html +++ b/src/postorius/doc/_build/html/development.html @@ -81,6 +81,22 @@ # class for views based on a single mailing list +
+

Development Workflow

+

The source code is hosted on Launchpad, which also means that we are using +Bazaar for version control.

+

Changes are usually not made directly in the project’s trunk branch, but in +feature-related personal branches, which get reviewed and then merged into +the trunk.

+

The ideal workflow would be like this:

+
    +
  1. File a bug to suggest a new feature or report a bug (or just pick one of +the existing bugs).
  2. +
  3. Create a new branch with your code changes.
  4. +
  5. Make a “merge proposal” to get your code reviewed and merged.
  6. +
+

Launchpad has a nice tour which describes all this in detail.

+

Writing View Code

When the work on Postorius was started, the standard way to write view code in @@ -257,6 +273,7 @@