Description of problem:

The rhdh_jira_lint.py script uses a YAML calendar (release_calendar.yaml) to determine release freeze phases (feature_freeze, code_freeze, ga_push) for enforcement. Currently, the calendar only includes .0 (minor) releases (e.g., 1.5.0, 1.6.0), not z-stream releases (1.5.1, 1.5.2, etc).

This resulted in issues assigned to z-stream versions being ignored (if not found) or falsely flagged (when using strict matching). We want to avoid both problems by:

• Treating z-stream versions as logically identical to their base .0 release (e.g., 1.5.1 uses 1.5.0's freeze schedule).

• Avoiding the maintenance overhead of tracking release dates for every z-stream.

Acceptance Criteria:

• Z-stream fix versions like 1.5.1, 1.6.2, etc., are automatically normalized to their base minor release (1.5.0, 1.6.0) during freeze phase evaluation.

• No false violations are raised for valid z-stream issues

• No need to add z-stream releases to release_calendar.yaml

• Slack message still shows the original fixVersion (e.g. 1.5.1) to maintain user context

• Logic is encapsulated and clearly documented