| 1 |
On Wed, 2015-11-11 at 11:28 +0100, Justin (jlec) wrote: |
| 2 |
> # Justin Lecher <jlec@g.o> (28 Feb 2015) |
| 3 |
> # Unfixed security problems |
| 4 |
> # No upstream support anymore |
| 5 |
> # CVE-2015-{0219,0220,0221,0222,5145} |
| 6 |
> # #536586 |
| 7 |
> # #554864 |
| 8 |
> =dev-python/django-1.4* |
| 9 |
> =dev-python/django-1.5* |
| 10 |
> =dev-python/django-1.6* |
| 11 |
> # Not supported by any django version upstream supports |
| 12 |
> dev-python/south |
| 13 |
> dev-python/Djblets |
| 14 |
> dev-util/reviewboard |
| 15 |
|
| 16 |
Reviewboard upstream is now maintaining its own version of django 1.6 |
| 17 |
for security fixes: https://www.reviewboard.org/news/2015/08/24/new-dja |
| 18 |
ngo-1-6-11-1-security-releases/ |
| 19 |
|
| 20 |
Would we be able to keep reviewboard in the tree (with a bump to the |
| 21 |
2.5.x versions) with this? |
| 22 |
|
| 23 |
Hans |
Archives