clandmeter/patchwork/docs, branch master

patchwork: Explicitly load states fixtures

2015-06-05T06:37:09+00:00

Apps with migrations will no longer load the initial_data fixtures by
default. In order to prepare to add migrations to patchwork, rename the
initial_data fixture to default_states (to match the default_tags
fixture), and explicitly load them in tests that require them.

Also, include this step in the INSTALL document.

Signed-off-by: Jeremy Kerr

cron: Move patchwork-cron script to a management command

2015-05-28T05:42:11+00:00

Signed-off-by: Jeremy Kerr

doc: Add NEWS file for recent updates

2015-05-28T02:24:54+00:00

... containing a guide to migrating to the recent changes.

Signed-off-by: Jeremy Kerr

Add patch tag infrastructure

2015-05-28T01:05:45+00:00

This change add patch 'tags', eg 'Acked-by' / 'Reviewed-by', etc., to
patchwork.

Tag parsing is implemented in the patch parser's extract_tags function,
which returns a Counter object of the tags in a comment. These are
stored in the PatchTag (keyed to Tag) objects associated with each
patch.

We need to ensure that the main patch lists do not cause per-patch
queries on the Patch.tags ManyToManyField (this would result in ~500
queries per page), so we introduce a new QuerySet (and Manager) for
Patch, adding a with_tag_counts() method to populate the tag counts in a
single query.

As users may be migrating from previous patchwork versions (ie, with no
tag counts in the database), we add a 'retag' management command.

Signed-off-by: Jeremy Kerr

docs: Add collectstatic step to installation instructions

2015-05-28T01:05:45+00:00

Because we're now using the staticfiles app, we need to run
collectstatic on init.

Signed-off-by: Jeremy Kerr

Update documentation and default settings to suit patchwork deployment model

2015-05-28T01:05:37+00:00

We've always allowed configuration without altering any of the
version-controlled files. With the recent settings changes, we have an
extra level of indirection with the dev/prod settings modules.

Since we have to edit a config file anyway, this change moves the
prod.py settings file to a template, which is then used directly by
mange.py (and the wsgi application).

Signed-off-by: Jeremy Kerr

docs: Fix documentation for new settings infrastructure

2015-05-27T02:29:04+00:00

A few tweaks for the INSTALL doc to update to the settings changes from
c641660e.

Signed-off-by: Jeremy Kerr

Move to a more recent django project structure

2015-05-27T02:26:41+00:00

This change updates patchwor to the newer project struture: we've moved
the actual application out of the apps/ directory, and the
patchwork-specific templates to under the patchwork application.

This gives us the manage.py script in the top-level now.

Signed-off-by: Jeremy Kerr

docs: Use 'prod' and 'dev' requirements files

2015-05-03T05:46:52+00:00

Django 1.5 and 1.6 are no longer supported.

    https://docs.djangoproject.com/en/dev/internals/release-process/

As a result, one should not encourage people to develop and/or deploy
against these versions - the latest version of Django supported by
patchwork (currently 1.7) should be used for both.

In addition, rather than duplicating shared requirements for 'dev' and
'prod' environments, move all shared requirements to a "base" file.

Signed-off-by: Stephen Finucane 
Signed-off-by: Jeremy Kerr

INSTALL: Fix indentation (whitespace only change) to 4 spaces

2015-03-22T13:17:33+00:00

Also, 2 newlines after each section.

Signed-off-by: Bryce Harrington 
Signed-off-by: Jeremy Kerr