Suggestion: Change versioning scheme

[DL6ER]

This repository provides a thin wrapper around mborsetti/webchanges which makes the latter easy to set up in a docker compose environment within seconds and is just awesome. However, it seems worth discussing IMO whether an independent versioning is really meaningful in this context. New releases of the container typically seem to be in sync with new releases of the underlying package.

My suggestion:

Instead of

• webchanges-docker:1.2.0 -> webchanges 3.26.0
• webchanges-docker:1.2.1 -> small changes, no webchanges update
• webchanges-docker:1.3.0 -> webchanges 3.30.0
• webchanges-docker:1.4.0 -> webchanges 3.31.0

I propose to use:

• webchanges-docker:3.26.0 -> webchanges 3.26.0
• webchanges-docker:3.26.0_1 -> small changes, no webchanges update
• webchanges-docker:3.30.0 -> webchanges 3.30.0
• webchanges-docker:3.31.0 -> webchanges 3.31.0

Whether the patch release would really be 3.26.0_1 or maybe 3.26.0.1 or 3.26.0p1 is, of course, separately debatable. In the end, the gain is that we would not need to do additional researching which version is in use when we can see this already based on the container image's version.

[yubiuser]

I've been thinking about this before. It's tricky to separate versioning from webchanges and the corresponding docker wrapper. Most often changes to webchanges will be the only thing that changes between two versions, but sometimes changes only to the wrapper will ocure.
I think, I'll go with a 1.2.4-r1 schema were -r denotes the 'wrapper' version.