I'm proposing two parallel release schemes:

* Annual release: This is to match Python release cycle (PEP 602) [1]
  so that we can have enough time to prepare for support for the new
  CPython version (mainly to wait for upstream packages to support it)
  and offer a truly stable, long-term-support repository.  During
  the (undecided) LTS lifetime, packages will only receive critical fixes.
* Weekly releases: We have been doing this for the first three releases [0]
  so far and I feel that it fit really well into modern human schedules.
  This also allows packages to stabilize, for example virtualenv updates
  embed wheels older than four weeks no more than every two weeks.
  Of course for the later goal, we will need branching every week
  and only allow critical bug fixes, i.e. freezing.
* The truly bleeding-edge repository can be obtained by publishing
  the current metadata.  However, we will not be doing this
  to discourage its use to casual users.

Note that the timings above are only based on speculations, nothing
is really coined and I would love to hear others' opinion on the matter.

[0] https://git.sr.ht/~cnx/ipwhl-data/refs
[1] https://www.python.org/dev/peps/pep-0602