RE: [PATCH 2/2] project: Provide a setting to only consider git send-email patches

[Finucane, Stephen]

> Hi Stephen,
> 
> > For the setup on patchwork.ozlabs.org, a flag for parsemail means I'd
> >> need project-specific configuration outside of the admin system, which
> >> seems a bit clunky.
> >
> > So you're suggesting...not including this option anywhere?
> 
> No, just that it should be a project setting (ie, part of the Project
> model), rather than something we pass as an argument to parsemail.

Ah, I hadn't considered the case where the person configuring a project 
wouldn't be the person maintaining the server/running the parsemail script. 
This is clearly a very common situation (example: ozlabs.org).

One point is that this patch doesn't have manual SQL migrations. However, as 
Django 1.6 is no longer supported upstream[1] and we now have some form of 
versioning[2], I feel comfortable dropping support ourselves. This also allows 
us to drop support for manual SQL migrations, thus sidestepping the issue 
entirely. Once I've merged the changes removing this support I will merge this.

Stephen

[1] https://www.djangoproject.com/download/#supported-versions
[2] https://lists.ozlabs.org/pipermail/patchwork/2015-October/001990.html

> Regards,
> 
> 
> Jeremy
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

[PATCH 0/3] Remove support for Django 1.6

[Stephen Finucane]

Django 1.6 is no longer supported, neither with feature bugfixes nor
security fixes. Additionally, Django 1.6 does not support the use of
Django Migrations, necessitating the continued use of manual SQL
migration files. Drop support for Django 1.6 thus encouraging users to
move to Django 1.7 or, ideally, Long Term Support (LTS) release 1.8.

Stephen Finucane (3):
  docs: Emphasise the deprecation of Django 1.6
  docs: Note removed support for Django 1.6
  tox: Remove the Django 1.6

 CHANGELOG.md | 4 +++-
 UPGRADING.md | 4 
 tox.ini  | 3 +--
 3 files changed, 8 insertions(+), 3 deletions(-)

-- 
2.0.0

___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

[PATCH] docs: Add XML-RPC to CHANGELOG

[Stephen Finucane]

This was missed in the patch.

Signed-off-by: Stephen Finucane 
---
 CHANGELOG.md | 4 
 1 file changed, 4 insertions(+)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 541df38..e87dbd7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,10 @@ This project adheres to [Semantic 
Versioning](http://semver.org/).
 
 ## [Unreleased]
 
+### Added
+
+- Automated documentation for the XML-RPC API. This can be found at '/xmlrpc'
+- Assorted cleanup tasks and bug fixes
 ...
 
 ## [1.0.0] - 2015-10-26
-- 
2.0.0

___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

[PATCH 3/3] tox: Remove the Django 1.6

[Stephen Finucane]

This version of Django 1.6 is no longer supported and there is no need
to test against it.

Signed-off-by: Stephen Finucane 
---
 tox.ini | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/tox.ini b/tox.ini
index d7eb5b0..c9b48c0 100644
--- a/tox.ini
+++ b/tox.ini
@@ -1,6 +1,6 @@
 [tox]
 minversion = 1.6
-envlist = {py27}-django{16,17,18}
+envlist = {py27}-django{17,18}
 skipsdist = True
 
 [testenv]
@@ -8,7 +8,6 @@ basepython =
 py27: python2.7
 deps =
 -r{toxinidir}/docs/requirements-dev.txt
-django16: django>=1.6,<1.7
 django17: django>=1.7,<1.8
 django18: django>=1.8,<1.9
 setenv =
-- 
2.0.0

___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

[PATCH 1/3] docs: Emphasise the deprecation of Django 1.6

[Stephen Finucane]

Though already mentioned in the CHANGELOG, the UPGRADING document
should describe plans to deprecate support for Django 1.6. This will
ensure sysadmins are not suprised when they attempt to upgrade.

Signed-off-by: Stephen Finucane 
---
 UPGRADING.md | 4 
 1 file changed, 4 insertions(+)

diff --git a/UPGRADING.md b/UPGRADING.md
index 3cf69d4..b302716 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -13,6 +13,10 @@ and re-run the grants script. For example, on postgres:
 psql -f lib/sql/migration/015-add-patch-tags.sql patchwork
 psql -f lib/sql/grant-all.postgres.sql patchwork
 
+We highly suggest you move to Django Migrations as support for Django 1.6
+(and subsequently manual SQL migrations) will be dropped in an upcoming
+release.
+
 ### Update to the new settings infrastructure
 
 By default, settings are read from `patchwork/settings/production.py`. To
-- 
2.0.0

___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

[PATCH 2/3] docs: Note removed support for Django 1.6

[Stephen Finucane]

Signed-off-by: Stephen Finucane 
---
 CHANGELOG.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 541df38..50f7089 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,7 +7,9 @@ This project adheres to [Semantic 
Versioning](http://semver.org/).
 
 ## [Unreleased]
 
-...
+### Removed
+
+- Support for Django 1.6
 
 ## [1.0.0] - 2015-10-26
 
-- 
2.0.0

___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

Patchwork instance for SNPS ARC Linux

[Alexey Brodkin]

Hello,

I'm wondering if there's a chance to get a patchwork project instance
for SNPS ARC Linux mailing list 
(http://lists.infradead.org/pipermail/linux-snps-arc/)
on http://patchwork.ozlabs.org/?

Regards,
Alexey
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

Re: Patchwork instance for SNPS ARC Linux

[Damien Lespiau]

On Mon, Nov 02, 2015 at 10:05:47AM +, Alexey Brodkin wrote:
> Hello,

Hi,

> I'm wondering if there's a chance to get a patchwork project instance
> for SNPS ARC Linux mailing list 
> (http://lists.infradead.org/pipermail/linux-snps-arc/)
> on http://patchwork.ozlabs.org/?

I can't help you with patchwork.ozlabs.org, it's all Jeremy's.

-- 
Damien
___
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork