3.2(.2) Release – is it officially out and stable or not? Documentation is misleading or possibly erroneous

[ds-clearago]

Issue Summary

1. Looking at GitHub Releases
   • 3.2 was released on Dec 23, 2022
   • 3.2.1 is not mentioned at all
   • 3.2.2 was released on Sep 1, 2023
   • No pre-release labels are set
2. Looking at PyPi
   • 3.2 was released on Dec 23, 2022
   • 3.2.1a0 was released Sep 1, 2023 as a pre-release
   • 3.2.2 was released on Oct 6, 2023
3. django-oscar:master is not behind v3.2
4. django-oscar:master is one commit behind v3.2.1a
   • (Always use the sphinx_rtd_theme)
5. django-oscar:master is 2 commits behind v3.2.1
   • But those 2 commits are not the same as from v3.2.1a
     • (3.2.1 final release)
     • (Update translations)
6. django-oscar:master is 4 commits behind v3.2.2
   • All of the 3 above + 3.2.2
7. The Sphinx documentation page
   • has a branch / version selector showing stable
     • no such branch is visible in this repo
     • maybe it refers to master here, but it's improbable as there is a 3.2.1 page that master is behind
   • The stable release page shows newest release v3.2.1 with release date: TBD
     • also the design is different to all other choices and seems somewhat broken as the navigation bar is missing most entries
   • There is no branch / version for v3.2.1 -> 404 https://django-oscar.readthedocs.io/en/3.2.1
   • The v3.2.2 release page shows newest release v3.2.2 with release date: TBD
   • The latest release page shows newest release v3.2.2 with release date: TBD
     • However, it doesn't have a page for v3.2.1 -> 404: https://django-oscar.readthedocs.io/en/latest/releases/v3.2.1.html

Questions

1. Was v3.2 released as stable LTS atm or not? When?
2. Was v3.2.1 released as stable LTS atm or not? When?
3. Was v3.2.2 released as stable LTS atm or not? When?
4. Is Sphinx docs stable matching a branch here?
5. What is the correct docs link to look at right now?

Steps to Reproduce

Visit Docs pages

[specialunderwear]

here is one part of the puzzle:

[ds-clearago]

Thanks @specialunderwear – that helps. @viggo-devries Do you mind also adjusting the docs accordingly?

Especially since the Slack message above can't be seen by people who aren't in the Slack channel already, and there's nothing in Discord yet
https://django-oscar.slack.com/archives/C1QSP0B51/p1697787788260089

Viggo de Vries
@hier We are closing down the oscar slack channel, because the auto inviter is broken and we can't seem to set up a new one.

->
(https://discord.com/channels/1164825981798854697/1164825982327328830/1185273345260916736):

Good evening everyone, glad to finally be able to reach this community after a year of trying to get past Slack inviter that seemingly ceased to work

Looks like the move from Slack to Discord is already adjusted in the docs (d791838 ), but the versions are still unclear...

[viggo-devries]

hi @ds-clearago

Something went wrong while releasing 3.2.1 release so I had to create it as 3.2.2, I see how this can be confusing.

unfortunately I cannot undo this. 3.2.1 was never released so we skipped this version and went straight to 3.2.2

I wanted to get this out ASAP because 3.2.2 supports Django 4 now which was quite important.

I changed the read the docs, I couldn't change the stable version unfortunately so I removed it for now and made the latest version the default.

Hope this helps.

[ds-clearago]

Hi @viggo-devries
Ah ok, thanks. That makes things clearer.

To close this issue, I think it would help to change these spots:

• https://github.com/django-oscar/django-oscar/blob/master/docs/source/releases/v3.2.2.rst?plain=1#L5 "TBD" to actual release date
• https://github.com/django-oscar/django-oscar/blob/master/docs/source/releases/v3.2.rst?plain=1#L5 "TBD" to actual release date
• Make master branch not be behind tag 3.2.2 anymore?

Maybe it also makes sense to create a /docs/source/releases/v3.2.1.rst file, only mentioning the above in there?