Display the release date on each release notes page

[roryokane]

Problem

Pages like https://ziglang.org/download/0.8.1/release-notes.html and https://ziglang.org/download/0.8.0/release-notes.html don’t display the date of those releases:

That is information I look for on a release notes page.

Proposed solution

I think the best place for the release date would be this heading:

www.ziglang.org/src/download/0.8.1/release-notes.html

Line 219 in 9de50d6

<h1>0.8.1 Release Notes</h1>

Making the release notes page look like this:

I haven’t found any template for all release notes files – I only found individual files for each release, such as src/download/0.8.1/release-notes.html and src/download/0.8.0/release-notes.html. So the above heading might have to be edited in each release-notes.html file.

Related code to reference when implementing

In this codebase, release dates are stored in data/releases.json.

The code to build https://ziglang.org/download/ includes release dates on its page. It gets the date like this:

www.ziglang.org/themes/ziglang-original/layouts/_default/downloads.html

Lines 11 to 12 in 9de50d6

	{{ range $release_name := $.Site.Params.downloads_release_order }}
	{{ $release := index $.Site.Data.releases $release_name }}

www.ziglang.org/themes/ziglang-original/layouts/_default/downloads.html

Line 16 in 9de50d6

<li>{{ index $release "date" }}</li>

[nektro]

That info is available here https://github.com/ziglang/zig/releases

It is bad practice to tie a release to a date.

[Atomk]

@nektro Any evidence supporting that "bad practice" claim? Rust, Go, Python, Swift, even release pages on Github all clearly show the release date.

It's useful information to contextualize the content of the page (i.e. some blog post linked to the 0.11.0 release notes and readers can easily see when that happened), it doesn't make sense to waste readers' time by having them look somewhere else for something this trivial.

For the same reason I am very glad that the News page (and posts finally) have dates too.

[nektro]

i disagree with my previous statement in this context. i might have misunderstood the request at first