Project and Release Planung:

Release Rules

We effectively have two hard gates every month:

Gate A (1st of the month): Consumption data must be imported cleanly and validated.

Gate B (7th of the month): Billing/subscriptions/invoice run must complete reliably.

This means a “billing-safe” release must be in production before the 1st if it changes import/mapping — or at the latest before the 7th if it only affects billing logic.

Rule: “We deploy to production only if it does not risk the upcoming 1st/7th billing cycle.”

Default approach: Deploy 2–4 days before the 1st, then only hotfixes.

Hotfix window: From the 1st to the 7th, fixes only — no new features.