Opened 16 months ago

Closed 16 months ago

Last modified 16 months ago

#21824 closed Uncategorized (fixed)

LTS not mentioned on Security policies page

Reported by: janfabry Owned by: tragiclifestories
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 Changed 16 months ago by bmispelon

  • Component changed from *.djangoproject.com to Documentation
  • Easy pickings set
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

Hi,

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

comment:2 Changed 16 months ago by tragiclifestories

  • Has patch set
  • Owner changed from nobody to tragiclifestories
  • Status changed from new to assigned

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 16 months ago by tragiclifestories (previous) (diff)

comment:3 Changed 16 months ago by timo

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

comment:4 Changed 16 months ago by tragiclifestories

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 Changed 16 months ago by Tim Graham <timograham@…>

  • Resolution set to fixed
  • Status changed from assigned to closed

In 4d8209431d2b1c97d86cf92992e6ddc1555c7ac7:

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

comment:6 Changed 16 months ago by Tim Graham <timograham@…>

In c539a4490f8c49bcd264d3d08c8686624cca6698:

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

Backport of 4d8209431d from master

comment:7 Changed 16 months ago by Tim Graham <timograham@…>

In 6ea5f9e0de8851f4fdb840d41da73c284c53bfba:

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

Backport of 4d8209431d from master

comment:8 Changed 16 months ago by janfabry

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

comment:9 Changed 16 months ago by timo

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