Release v4.0.2

[lsm5]

As the title says.

Tag v4.0.2 already added to the Bump to v4.0.2 commit.

@containers/podman-maintainers PTAL

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lsm5]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ashley-cui]

LGTM!

[TomSweeneyRedHat]

LGTM
thanks @lsm5 !

[TomSweeneyRedHat]

/lgtm
/hold # on tests

[rhatdan]

/hold cancel

[TomSweeneyRedHat]

@lsm5 Can you create a tag/release for 4.0.2 please?

[vrothberg]

If we're using the v4.0 branch in RHEL, we're doing it wrong. RHEL should only consume -rhel suffixed branches. But a v4.0-rhel doesn't seem to exist yet. We need to create one and revert this commit there.

@mheon @baude PTAL

[lsm5]

Can we please revert this @lsm5 ? The v4.0 branch is a maintenance branch. This change would mean users will see invalid version "4.0.3-dev" while doing "podman version" for debugging purposes. We were bitten by this multiple times in the past. In essence this branch is just 4.0.2 + backports. Thanks!

@jnovy Reverting a tagged release is going to be really painful. I think we best not revert. When I last did the rhel build, I didn't use HEAD from v4.0 but the commit id that bumped version from v4.0.2-dev to v4.0.2. So, unless that's changed in the rhel spec file, I would say we're good.