test

> Nobody can keep track of all the changes and release notes document what
> has happened since the last tagged release. This means that we can
> verify that progress happens and what changes were done to the language
> or stdlib, even if you lost track of the language for months

I feel like a better solution for that would be a running changelog of
breaking changes and new features (bugfixes being less crucial to
include here). Annotate it with dates and maybe commit hashes / links
to PRs. Add a big heading or something where releases were cut. It
could be a simple file included in the zig repo that is easy for anyone
to update via PR.

> I usually track master with one to two days delay, but even i can't keep
> track of all changes and i miss a lot of important stuff. So the release

Anecdotally, it seems like a large proportion of people are tracking
master. The ziglearn site recommends to use master. And when people
ask a question (e.g. on IRC) and it turns out they are using a tagged
release, the first thing is always to get them on master, even if it's
not relevant to their problem.

So why spend so much time on release notes?

I've seen how much work Andrew puts into them (the page up now
mentions that it takes over a week), the kind of work which must be at
least a little soul-destroying. And it ends up being a very, very long
page to read. Maybe useful mainly as a reference, but how useful is a
version-by-version changelog when most people are tracking master.

> This matches what Jetforce does, so take it up with them first.

Done: https://github.com/michael-lazar/jetforce/pull/43

---
 src/serve.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/serve.c b/src/serve.c
index 74bb979..e32b389 100644
--- a/src/serve.c
+++ b/src/serve.c
@@ -167,7 +167,7 @@ serve_cgi(struct gmnisrv_client *client, const char *path,
 		assert(addrs);
 
 		// Compatible with Jetforce
-		setenv("GATEWAY_INTERFACE", "GCI/1.1", 1);
+		setenv("GATEWAY_INTERFACE", "CGI/1.1", 1);
[message trimmed]

---
 your-name | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 your-name

diff --git a/your-name b/your-name
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/your-name
@@ -0,0 +1 @@
+I'm about to try git send-email
-- 
2.20.1
[message trimmed]