[Django] #32431: Consider listing the history of security issues in reverse chronological order

32 views
Skip to first unread message

Django

unread,
Feb 8, 2021, 8:19:25 AM2/8/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
------------------------------------------------+------------------------
Reporter: Jaap Roes | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Because of the recent CVE fix I was searching Google for "django cve"
which brought me to
https://docs.djangoproject.com/en/3.1/releases/security/.

This is a super helpful page, except that the most recently fixed (an
therefore most relevant) security issues are listed all the way at the
bottom of the page. I would expect them to be at the top of the page.

--
Ticket URL: <https://code.djangoproject.com/ticket/32431>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Feb 9, 2021, 9:51:28 AM2/9/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
--------------------------------------+------------------------------------

Reporter: Jaap Roes | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):

* easy: 0 => 1
* stage: Unreviewed => Accepted


Comment:

Hey Jaap, OK yes, I guess :) (I've half thought this myself at times
so...)

--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:1>

Django

unread,
Feb 10, 2021, 3:20:52 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master

Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Hasan Ramezani):

* owner: nobody => Hasan Ramezani
* status: new => assigned


--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:2>

Django

unread,
Feb 10, 2021, 4:12:45 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master

Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Jaap Roes):

I just noticed the footer on that page links to the release notes of
Django 0.95. I guess this is automatically added by Sphinx, but it is
somewhat strange as well. Would moving the
[https://github.com/django/django/blob/9c6ba876928fd20194ac3238dc06aeae66d7bd50/docs/releases/index.txt#L373
Security releases section] on
https://docs.djangoproject.com/en/3.1/releases/ to the top "fix" that
link? It would also make the security release page slightly more
discoverable.

--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:3>

Django

unread,
Feb 10, 2021, 6:26:44 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master

Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Hasan Ramezani):

* has_patch: 0 => 1


Comment:

I've created a [https://github.com/django/django/pull/13993 PR] and moved
`Issues under Django's security process` to the top and `Issues prior to
Django's security process` to the bottom.
Also, I used a small python script to reverse the order of entries.

Jaap

I just noticed the footer on that page links to the release notes of
Django 0.95. I guess this is automatically added by Sphinx

Yes, it's added by Sphinx.

Would moving the ​Security releases section on


https://docs.djangoproject.com/en/3.1/releases/ to the top "fix" that
link?

Yes, By this change, the release index page will be the previous page of
the `Security Issues` page.

Carlton, Shall we go for this change as well?

--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:4>

Django

unread,
Feb 10, 2021, 9:38:33 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master

Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Carlton Gibson):

I don't think we should move the **Security Releases** section to the top.

The vast majority of our users are looking for the latest release, by
series, be they security or not, and not the list of security issues.
That 0.95 is the previous page in the docs is just how it is (for me) —
not a biggie.

--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:5>

Django

unread,
Feb 10, 2021, 9:47:00 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

* stage: Accepted => Ready for checkin


--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:6>

Django

unread,
Feb 10, 2021, 10:02:55 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed

Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson <carlton@…>):

* status: assigned => closed
* resolution: => fixed


Comment:

In [changeset:"17a5e2cff606305fd819a024cf9f450f90202a6f" 17a5e2cf]:
{{{
#!CommitTicketReference repository=""
revision="17a5e2cff606305fd819a024cf9f450f90202a6f"
Fixed #32431 -- Reversed order of security issues history.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:7>

Django

unread,
Feb 10, 2021, 10:03:52 AM2/10/21
to django-...@googlegroups.com
#32431: Consider listing the history of security issues in reverse chronological
order
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: Hasan
Type: | Ramezani
Cleanup/optimization | Status: closed
Component: Documentation | Version: master

Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Carlton Gibson <carlton.gibson@…>):

In [changeset:"dd14e639ad8d50c69f5f133278db13c2812d6e54" dd14e63]:
{{{
#!CommitTicketReference repository=""
revision="dd14e639ad8d50c69f5f133278db13c2812d6e54"
[3.2.x] Fixed #32431 -- Reversed order of security issues history.

Backport of 17a5e2cff606305fd819a024cf9f450f90202a6f from master
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/32431#comment:8>

Reply all
Reply to author
Forward
0 new messages