rel 0.9.74

[netblue30]

New release coming in the next few days, a huge one - we have at least two years of code and profiles there. I still have to do some testing. So, please only new profiles and fixes from pull requests. Landlock will remain experimental for now, I'm waiting for the new Debian release to get some sort of baseline for the Linux kernel.

We will follow with a small point release in about two months, fixing whatever bugs are coming.Thanks!

Relates to:

• Release 0.9.74 discussion #5597

[kmk3]

Nice.

Regarding the release, could you use annotated tags for new rc/release tags?

Some git commands either ignore lightweight tags or they may end up selecting a
tag that unrelated to versioning when using git describe (depending on the
result of sorting the tags). Also, annotated tags contain their creation date.

It would be nice to have them GPG-signed with git tag -s, but just using
git tag -a would already be a big improvement. The tag message can be
something trivial like "RC" or "Release".

From git-tag(1):

Tag objects (created with -a, -s, or -u) are called "annotated" tags;
they contain a creation date, the tagger name and e-mail, a tagging
message, and an optional GnuPG signature. Whereas a "lightweight" tag
is simply a name for an object (usually a commit object).

Annotated tags are meant for release while lightweight tags are meant
for private or temporary object labels. For this reason, some git
commands for naming objects (like git describe) will ignore lightweight
tags by default.

[netblue30]

Sure, I'll go with "git -s", thanks. Lately I've been using the automatic tagging in the release tool here on github website. Apparently the tool is doing regular lightweight tags.

Release tomorrow morning (Mar 25).

[netblue30]

All set! Moving to devel version 0.9.75

I've run into some problems with signing the tag:

$ git tag -s 0.9.74 -m "release 0.9.74"
error: gpg failed to sign the data
error: unable to sign the tag

so I ended up going with git tag -a