# Contributing

The package is maintained via https://salsa.debian.org/debian/debian-security-support
so everyone in the Debian group on salsa has direct commit access. Please use
it, wisely.

All changes should be introduced in unstable first, and then migrate to testing.
To support stable and older releases there are GIT branches.

Only support status updates are applied to stable and older branches.

If in doubt whether something should be committed for unstable,
please open a MR on salsa.debian.org so the change can be discussed there.

Further improvements to this README are very welcome too.

# ToDo list for a new Debian release

At the beginning of each new Debian release cycle, these steps need to be done:
- create a new git branch for the old release
- increase the epoch in debian/changelog
- create security-support-ended.debX based on the previous release
- check-support-status.in:
  - increase DEB_LOWEST_VER_ID and drop security-support-ended.debY

At a later point, possibly the freeze, these steps need to be done:
- debian/rules: increase NEXT_VERSION_ID
- check-support-status.in:
  - increase DEB_NEXT_VER_ID
- update links with release codenames in security-support-limited

