[Django] #32878: Seems that browsing releases in Django Project website interchanged "Prev" and "Next" links

[Django]

#32878: Seems that browsing releases in Django Project website interchanged "Prev"
and "Next" links
-------------------------------------+-------------------------------------
Reporter: Igor | Owner: nobody
Kuivjogi Fernandes |
Type: | Status: new
Cleanup/optimization |
Component: | Version: 3.2
Documentation |
Severity: Normal | Keywords: links releases
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I was navigating inside the 3.2.4 release
(https://docs.djangoproject.com/en/3.2/releases/3.2.4/) and found
something in the sidebar at Browse section:
- the **Prev** link leads to 3.2.5 release
- the **Next** link leads to 3.2.3 release

Should not it to be the opposite, i.e., **Prev** leads to 3.2.3 and
**Next** leads to 3.2.5 ?

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

[Django]

#32878: Seems that browsing releases in Django Project website interchanged "Prev"
and "Next" links
-------------------------------------+-------------------------------------

Reporter: Igor Kuivjogi | Owner: nobody

Fernandes |
Type: | Status: new
Cleanup/optimization |

Component: Documentation | Version: 3.2
Severity: Normal | Resolution:

Keywords: links releases | Triage Stage:

| Unreviewed
Has patch: 0 | Needs documentation: 0

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

Changes (by Igor Kuivjogi Fernandes):

* Attachment "django-releases.png" added.

Browsing releases

[Django]

#32878: Seems that browsing releases in Django Project website interchanged "Prev"
and "Next" links
-------------------------------------+-------------------------------------

Reporter: Igor Kuivjogi | Owner: nobody
Fernandes |

Type: | Status: closed

Cleanup/optimization |
Component: Documentation | Version: 3.2

Severity: Normal | Resolution: invalid

Keywords: links releases | Triage Stage:

| Unreviewed
Has patch: 0 | Needs documentation: 0

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

Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => invalid

Comment:

Thanks for the report, however as far as I'm aware it's not something that
we can change (Sphinx builds docs that way). Release are sorted like this
to keep the latest version at the top, see
[https://docs.djangoproject.com/en/3.2/releases/ Release notes].

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

[Django]

#32878: Seems that browsing releases in Django Project website interchanged "Prev"
and "Next" links
-------------------------------------+-------------------------------------

Reporter: Igor Kuivjogi | Owner: nobody
Fernandes |
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.2
Severity: Normal | Resolution: invalid

Keywords: links releases | Triage Stage:

| Unreviewed
Has patch: 0 | Needs documentation: 0

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

Comment (by Nick Pope):

The release notes are listed from newer to older releases, see
https://docs.djangoproject.com/en/stable/releases/. As such, when viewing
the release notes for 3.2.4, the ''previous page'' is for 3.2.5 and the
''next page'' is for 3.2.3.

The previous and next links at the bottom of the page and in the sidebar
are moving backward and forward between documentation pages and are not
specific to the release note pages, nor release versions. I can see how
this may be confusing when looked at only in the context of the releases,
but it is not possible to change without reordering the release notes to
be in non-reverse order.

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