since it is now managed automatically by versioneer.
Instead, suggest creating a "next" maintainance branch.
But stop using `-` and `.` characters in it, to type it faster, since
most of the new branches will be based on it.

since now sbws version is calculated from last release tag.

Since it is now done by `versioneer`.

releases can live now in gitlab.tpo, instead of github.com and
there is no need to check them since Gitlab is FLOSS and gitlab.tpo is
hosted by Tor Project.

Also, stop assuming which is the current branch and remote and do not
push. Instead guide the maintainer to do it.

fix: tests: Create new authority keys

Closes #33150 and #34394

See merge request tpo/network-health/sbws!10

at the beginning of the line and in empty lines. They are not needed.

Closes: #33473

add link to it and rephrase some sentences.

and measurement attempts from all the results.
Until they get properly updated.

Also change dates in tests, so that timestamps are counted correctly

Closes: #34309.

Maint 1.1 bug33871 scaling 03

See merge request tpo/network-health/sbws!9

ahem, because of all json it has to manage in memory.

or testing and add links.

because sometimes the package might not be in Debian stable or testing
and we are not checking Ubuntu releases.

because they expired.
They will expire again in a year.
Implementing #33150 and using chutney would avoid to update keys.

Closes #34394.

Closes #33871.

so that it has its own page as it is too long as docstring and is
harder to write latex with the docstring syntax.

and without consensus bw from scaling.

Part of #33871, closes #33831.

since rounding already returns 1 as minimum.

instead of bw before scaling.

Tests have finally correct value.
For 1 result, only when the cap is 1, the value will be equal to the
rounded bw because the cap does not limit it.

Make tests pass because the high limit change the expected values,
but the final value still needs to be fixed.

Make test pass, though the value is not correct since it needs to be
rounded after clipping

Take either the consenus bandwidth or the descriptor bandwidth if
one of them is missing, do not scale when both are missing and
ignore descriptor average and burst when they are missing.

Scale relays without average or observed bandwidth.
Later it will be check what to do if their values are None or 0

since they are probably due a bug.