Release Lifecycle

The core rule

Fred releases one production version at a time.

There is no long-running parallel maintenance of multiple major versions. Swift 3.x is the current production release. Kea 1.5 is obsolete; Weaver 5.x is feature complete and in validation.

Branch model

main     ← always the live, deployed production state
develop  ← where the next version is being built

That is the complete branch topology for the Fred website, and for the Fred platform itself.

Hotfixes

When a bug is found in production:

  1. Branch from main — hotfix/short-description
  2. Fix and merge back to main
  3. Cherry-pick the same fix to develop immediately

Step 3 is mandatory. A fix that does not land on develop will reappear in the next release.

When a new major version ships

  1. develop is merged to main — the new version is live
  2. A v{major}.{minor}-{codename} tag is cut from the pre-merge state of main as a frozen snapshot
  3. The previous release enters the support window (hotfixes only, no new features)

Release naming

Fred releases carry bird codenames:

CodenameVersionStatus
Kea1.5.xObsolete
Swift3.xProduction — stable
Weaver5.xFeature complete — in validation

The name is chosen to reflect a character of the release, not just a label.

Support windows

EventSupport status
New major GAPrevious release enters support window
Support windowHotfixes and security patches only
End of windowNo further patches; operators should have migrated

See the release overview for the current status of each generation.

For contributors

Target develop for all new work. Do not open pull requests against main except for hotfixes.

If you are unsure whether something is a hotfix or a feature, open it against develop. The maintainers will backport it to main if urgency requires.