RFC: אסטרטגיית גרסאות חדשה עבור Discourse

מפתח
43

That’s pretty cool :+1:

Do I understand correctly that there is no stable update to 3.5.3 now, possibly coincidentally?

4 לייקים
44

Yeah, just a coincidence. We didn’t have any security fixes to release this month.

Stable 3.5 is still fully supported

6 לייקים
45

Hi,

I used to use the beta tag and am now trying to update my scripts to use the new setup. Here’s how the repository looks as far as I can tell:

* b541e99ea2 (origin/tests-passed, origin/main, origin/latest) DEV: Exclude new table in IntermediateDB config
* 02dfb651ae DEV: Add support for converting and importing `category_moderation_groups`
.
.
.
* 1dde082e96 UX: update lightbox quote icon to apply shadow (#36247)
* 3e7317b334 (tag: v2025.12.0-latest, tag: release) DEV: Begin development of v2025.12.0-latest (#36249)
| * 48167b94d6 (origin/release/2025.11) Backport limited body overflow (#36256)
| * 75d61b40ee (tag: v2025.11.0) DEV: Bump version on `release/2025.11` to `v2025.11.0` (#36251)
|/  
* e3f0320395 FIX: uses overflow hidden body on iOS (#36248)
.
.
.
* 05cd20d401 Bump version to v3.6.0.beta3-latest
* 8a3cb59d5b (tag: v3.6.0.beta2, tag: latest-release, tag: beta) Bump version to v3.6.0.beta2
* 21e5ded097 DEV: remove redundant data attr when cooking posts (#35650)
  • Is it expected that the beta tag is still pointing at v3.6.0.beta2?
  • Is it expected that the release tag is not pointing to a revision on the release/2025.11 branch?

Thanks :slight_smile:

2 לייקים
46

Hi @simonk, thanks for raising those points! We’ve actually been discussing both those things today internally.

  • The old beta and latest-release tags should be aliases of release

  • release should be tracking the latest commit of release/2025.11

Working on getting that fixed up right now.

2 לייקים
47

Those three tags have now been moved to the correct commit manually. Will make sure that the automated tooling is updated to keep them in the right place going forward.

* commit 48167b94d63faf8a41b9c8193ec5dd3e4e9f498e (HEAD -> release/2025.11, tag: release, tag: latest-release, tag: beta, origin/release/2025.11)
| Author: Joffrey JAFFEUX <j.jaffeux@gmail.com>
| Date:   Wed Nov 26 14:31:55 2025 +0100
| 
|     Backport limited body overflow (#36256)
|
5 לייקים
48

A production quirk.

My self-hosted Discourse was still showing 3.6.0.beta2 as the most recent release. In the Admin Dashboard, the green smiley face indicated I was on the latest release, but in reality, I was two releases behind.

I performed a manual update and am now on 2025.12.0-latest.

Is there something you can do in the release tool to flag 3.6.0.beta2 as outdated and require an update?

2 לייקים
49

A post was split to a new topic: Translation restructuring on crowdin for new-versioning-strategy

50

So this is probably because of the transition from one scheme to the new one, but

  • yesterday 3.5.4 was released
  • 3.5 is marked ESR and was released in August 2025
  • yesterday 2026.1 was released which is an ESR version

but 3.5 is now marked end-of-life. According to the above it would be supported until the end of March?

Also, that page says Jan 28 is “today”.

image
image930×344 5.76 KB

51

Yeah that’s correct. Stable 3.5 doesn’t have its own branch in git, so continuing to support it after converting the stable branch to a tag is tricky. We did tag v3.5.4 (which includes the latest security fixes) just before deleting the stable branch, so it’s ok to use that if you need a little more time before jumping to 2026.1. But any future security fixes will not be available for the 3.5 series.

Once we release 2026.7 ESR, there will be two months where we continue to support 2026.1 on its release branch.

Will take a look at this, thanks.

5 לייקים