zostera / django-marina / 33152868608

100%

push

github

Add a maintenance-round section to MAINTAINING.md (#673)

* Add a maintenance-round section to MAINTAINING.md

The version support policy already says to track endoflife.date, but
nothing said when to look. Makes it the first step of a maintenance
round and of every release, so the matrix gets reconciled against
reality rather than from memory.

Calls out that tox.ini, ci.yml and pyproject.toml drift independently
and must be checked together, and that dropping a cycle is a breaking
change whose only signal to users is the CHANGELOG entry, since the
YY.N version number carries none.

Also records the release-note ordering convention: dropped
Python/Django first, then added, then the rest.

Audited all five repos against endoflife.date while writing this. All
are already current: Python 3.10-3.14 and Django 5.2/6.0/6.1 plus main,
with tox.ini, ci.yml and pyproject.toml in agreement everywhere. Nothing
to drop or add today. Python 3.10 goes EOL 2026-10-31, so the next round
will drop it.

* Expand the release-note ordering convention

Full category order: security, dropped, added, fixes, features, tooling,
other. Records why fixes sort above features (the audience is upgraders,
not shoppers) and why security sorts above the support matrix.

Also adds a **Breaking:** prefix convention for behavior changes that
would otherwise read as routine bug fixes.

* Update PACKAGING.md for the new MAINTAINING.md shape

MAINTAINING.md gains a maintenance-round section, so it is no longer
two sections. The 'two-section shape' wording was already wrong for
bootstrap3 and bootstrap4, which add a maintenance-mode section.

28 of 28 branches covered (100.0%)

Branch coverage included in aggregate %.

164 of 164 relevant lines covered (100.0%)

14.0 hits per line