Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#21824 closed Uncategorized (fixed)

LTS not mentioned on Security policies page

Reported by: Jan Fabry Owned by: James Turley
Component: Documentation Version: 1.6
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

The "Django security policies" page doesn't mention 1.4 as an LTS release under the "Supported versions" section, giving the impression that it doesn't receive any updates anymore, while the "release process" page has been updated, so now the docs are inconsistent.

https://github.com/django/django/blob/master/docs/internals/security.txt#L48

Change History (9)

comment:1 by Baptiste Mispelon, 10 years ago

Component: *.djangoproject.comDocumentation
Easy pickings: set
Triage Stage: UnreviewedAccepted

Hi,

Indeed, the existence of an LTS release should be mentionned there.

comment:2 by James Turley, 10 years ago

Has patch: set
Owner: changed from nobody to James Turley
Status: newassigned

Corrected:

https://github.com/tragiclifestories/django/tree/ticket_21824

Sphinx is not building at all for me, however (before or after I made the change), so I will need to puzzle that out before making a pull request. (Unless someone else has a second to check.)

Last edited 10 years ago by James Turley (previous) (diff)

comment:3 by Tim Graham, 10 years ago

I created a pull request and left comments. If you have problems with sphinx, feel free to seek help in #django-dev.

comment:4 by James Turley, 10 years ago

Thanks Tim. Just made another commit linking to release-process as you suggest. Downgrading to Sphinx 1.2.0 got the thing building and I can confirm that it builds without warnings to HTML with the correct :ref: link in place.

Looks like there could be some compatibility issue with Sphinx 1.2.1 (which only released last week); will investigate further and raise a ticket to see if it can be reproduced by anyone else.

comment:5 by Tim Graham <timograham@…>, 10 years ago

Resolution: fixed
Status: assignedclosed

In 4d8209431d2b1c97d86cf92992e6ddc1555c7ac7:

Fixed #21824 -- Added reference to LTS in docs/internals/security.txt

comment:6 by Tim Graham <timograham@…>, 10 years ago

In c539a4490f8c49bcd264d3d08c8686624cca6698:

[1.5.x] Fixed #21824 -- Added reference to LTS in docs/internals/security.txt

Backport of 4d8209431d from master

comment:7 by Tim Graham <timograham@…>, 10 years ago

In 6ea5f9e0de8851f4fdb840d41da73c284c53bfba:

[1.6.x] Fixed #21824 -- Added reference to LTS in docs/internals/security.txt

Backport of 4d8209431d from master

comment:8 by Jan Fabry, 10 years ago

Should this also be backported to the 1.4.x branch? It's still supported, according to the LTS policy :-)

comment:9 by Tim Graham, 10 years ago

I tried but docs/internals/security.txt isn't present on the 1.4 branch and I don't think it's worth adding it.

Note: See TracTickets for help on using tickets.
Back to Top