redesign releases page to better show the current versions #597

oliverpool commented 2025年06月25日 23:28:27 +02:00

Current releases page

image

Proposed updated releases page - Timeline example - Discontinued example

image

• the releases pages now prominently shows:
  • which versions are supported
  • until when a given version will be supported
  • link to the install documentation
  • link to the security-announcement repo
  • link to the release schedule
  • links to all blog-posts related to a major version
• instead of a linear pagination, each major release gets a page with all versions (arguably the 1.x page has multiple major versions, but I think this is fine)

As currently, the releases page still shows:

• a link to the maintenance policy
• links to older versions
• links to the binary, container images and release notes

### [Current releases page](https://forgejo.org/releases/)  ### [Proposed updated releases page](https://forgejo.codeberg.page/@pull_597/releases/) - [Timeline example](https://forgejo.codeberg.page/@pull_597/releases/11.x/) - [Discontinued example](https://forgejo.codeberg.page/@pull_597/releases/10.x/)  - the releases pages now prominently shows: - which versions are supported - until when a given version will be supported - link to the install documentation - link to the security-announcement repo - link to the release schedule - links to **all** blog-posts related to a major version - instead of a linear pagination, each major release gets a page with all versions (arguably the [1.x page](https://forgejo.codeberg.page/@pull_597/releases/1.x/) has multiple major versions, but I think this is fine) As currently, the releases page still shows: - a link to the maintenance policy - links to older versions - links to the binary, container images and release notes

forgejo-website commented 2025年06月25日 23:47:06 +02:00

Preview ready: https://forgejo.codeberg.page/@pull_597/
https://forgejo.codeberg.page/@pull_597/releases/1.x/
https://forgejo.codeberg.page/@pull_597/releases/5/
https://forgejo.codeberg.page/@pull_597/releases/6/
https://forgejo.codeberg.page/@pull_597/releases/4/
https://forgejo.codeberg.page/@pull_597/releases/10.x/

Preview ready: https://forgejo.codeberg.page/@pull_597/ https://forgejo.codeberg.page/@pull_597/releases/1.x/ https://forgejo.codeberg.page/@pull_597/releases/5/ https://forgejo.codeberg.page/@pull_597/releases/6/ https://forgejo.codeberg.page/@pull_597/releases/4/ https://forgejo.codeberg.page/@pull_597/releases/10.x/

mahlzahn commented 2025年06月26日 01:19:33 +02:00

Timeline

1. v11.0
2. releases lower first letter
3. RSS symbol leads to RSS for all releases. Maybe just drop it? (Also a bit off on mobile view)
4. Add link to documentation (# or at bottom)
5. lower case end of life, add link to release schedule
6. Maybe dashed line towards end of life

### Timeline 1. v11.0 1. releases lower first letter 2. RSS symbol leads to RSS for all releases. Maybe just drop it? (Also a bit off on mobile view) 3. Add link to documentation (# or at bottom) 4. lower case end of life, add link to release schedule 5. Maybe dashed line towards end of life 

mahlzahn commented 2025年06月26日 01:42:28 +02:00

Overall releases

1. Title with lower first character of releases
2. v7.0 to match this version slug everywhere, e.g. in documentation
3. spacing looks a bit weird to my eyes
4. There is only ohe announcement per release. I'd expect also this to show up in announcements? https://forgejo.codeberg.page/@pull_597/2025-02-release-v10-0-1/. Also, here the spacing seems a bit weird?
5. Remove the arrow, we don't use it anywhere for links.
6. Maybe Versions history instead of timeline?
7. watch the repo or subscribe to its RSS feed (+link to RSS feed)
8. v10.0 v9.0 v8.0 v7.0
9. Split 1.x to v1.21 v1.20 v1.19 v1.18. Thus, also for the timelines and it matches the docs versions.

Screenshot_20250626-012056_2.png

### Overall releases 1. Title with lower first character of releases 1. v7.0 to match this version slug everywhere, e.g. in documentation 2. spacing looks a bit weird to my eyes 3. There is only ohe announcement per release. I'd expect also this to show up in announcements? https://forgejo.codeberg.page/@pull_597/2025-02-release-v10-0-1/. Also, here the spacing seems a bit weird? 4. Remove the arrow, we don't use it anywhere for links. 5. Maybe Versions history instead of timeline? 6. watch the repo or subscribe to its RSS feed (+link to RSS feed) 7. v10.0 v9.0 v8.0 v7.0 8. Split 1.x to v1.21 v1.20 v1.19 v1.18. Thus, also for the timelines and it matches the docs versions. 

oliverpool commented 2025年06月26日 10:30:14 +02:00

Thank you all for the constructive feedback!

Release Announcements / Blog posts

This should be centered, but currently isn't?

spacing looks a bit weird to my eyes

There is only one announcement per release

Remove the arrow, we don't use it anywhere for links.

I wanted to list all the announcement for a given major version. For instance 10.x has 2 blog posts (https://forgejo.org/2025-02-release-v10-0-1/ and https://forgejo.org/2025-01-release-v10-0/).
Aligning such unknown-length list is tricky and I wasn't very happy myself...

After some further tests, I would propose the following:

• inline links (instead of one line per link)
• not colored, to not disturb the balance
• further below
• without arrows

Here is how it would have looked during 10.x maintenance window:
image

v11.0 vs 11.x

v11.0

v7.0 to match this version slug everywhere, e.g. in documentation

I think there is a bigger discussion that should happen (preferably in a separate issue?) regarding major and minor versions.
Forgejo initially inherited the habit of incrementing minor version with breaking changes (1.20, 1.21).
After adapting semver, the minor version doesn't seem to be used anymore (10.0.x).

But as far as I know, a new minor version could exist at some point (11.1.0 with a migration for instance, if migrations need a minor bump, as proposed in forgejo/governance#124)

v10.0 v9.0 v8.0 v7.0

The release schedule uses 10.0, while the precise releases usually have the v prefix. I kept this convention (use of v only for precise versions) but I can switch to always use the v prefix.

Miscellaneous adjustments

I took into account the following suggestions.

releases lower first letter

RSS symbol leads to RSS for all releases. Maybe just drop it?

lower case end of life, add link to release schedule

Title with lower first character of releases

Maybe Versions history instead of timeline?

I went with All versions

watch the repo or subscribe to its RSS feed (+link to RSS feed)

Future work

I don't see any easy way to implement the following suggestions, so I would like to mark them as "out-of-scope" for this PR. They can be implemented later by anyone motivated:

Add link to documentation (# or at bottom)

Maybe dashed line towards end of life

Split 1.x to v1.21 v1.20 v1.19 v1.18. Thus, also for the timelines and it matches the docs versions.

Thank you all for the constructive feedback! ### Release Announcements / Blog posts > This should be centered, but currently isn't? > spacing looks a bit weird to my eyes > There is only one announcement per release > Remove the arrow, we don't use it anywhere for links. I wanted to list all the announcement for a given major version. For instance 10.x has 2 blog posts (https://forgejo.org/2025-02-release-v10-0-1/ and https://forgejo.org/2025-01-release-v10-0/). Aligning such unknown-length list is tricky and I wasn't very happy myself... After some further tests, I would [propose the following](https://forgejo.codeberg.page/@pull_597/releases/): - inline links (instead of one line per link) - not colored, to not disturb the balance - further below - without arrows Here is how it would have looked during 10.x maintenance window:  ### v11.0 vs 11.x > v11.0 > v7.0 to match this version slug everywhere, e.g. in documentation I think there is a bigger discussion that should happen (preferably in a separate issue?) regarding major and minor versions. Forgejo initially inherited the habit of incrementing minor version with breaking changes (1.20, 1.21). After adapting semver, the minor version doesn't seem to be used anymore (10.0.x). But as far as I know, a new minor version could exist at some point (11.1.0 with a [migration](https://codeberg.org/forgejo/forgejo/pulls/8258) for instance, if migrations need a minor bump, as proposed in https://codeberg.org/forgejo/governance/issues/124) > v10.0 v9.0 v8.0 v7.0 The [release schedule](https://forgejo.org/docs/latest/admin/release-schedule/) uses `10.0`, while the precise releases usually have the `v` prefix. I kept this convention (use of `v` only for precise versions) but I can switch to always use the `v` prefix. ### Miscellaneous adjustments I took into account the following suggestions. > releases lower first letter > RSS symbol leads to RSS for all releases. Maybe just drop it? > lower case end of life, add link to release schedule > Title with lower first character of releases > Maybe Versions history instead of timeline? I went with `All versions` > watch the repo or subscribe to its RSS feed (+link to RSS feed) ### Future work I don't see any easy way to implement the following suggestions, so I would like to mark them as "out-of-scope" for this PR. They can be implemented later by anyone motivated: > Add link to documentation (# or at bottom) > Maybe dashed line towards end of life > Split 1.x to v1.21 v1.20 v1.19 v1.18. Thus, also for the timelines and it matches the docs versions.