Do you know semver?

[Pierozi]

Guys do you know what semver is for real?

You cannot accept to bump chromium driver without increasing, AT LEAST, the patch version.
Having a BC break between 3.4.0-chromium and 3.4.0-francium is unacceptable.

Related : #559

[lmtierney]

https://github.com/SeleniumHQ/docker-selenium/wiki/Tagging-Convention

[Pierozi]

Right, and this is not semver...
Patch are just useless in this case

[Pierozi]

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.

[lmtierney]

Was there somewhere stating that the project follows this exactly?

If a new chromedriver comes out that supports the new Chrome version that came out, you want to wait until the selenium project itself comes out with a new release even if using Chrome is broken without it?

[Pierozi]

You are not forced to follow the Selenium version, the thing is between two tags with the same PATCH version you iterate some changes.

If the -<Chemical Element in Alphabetical order> was only to identify new build on same github tag, to identify an immutable image state, that's fine.

But introduce an update of chrome driver (or any other change actually) is not.

[ddavison]

We follow the versioning of selenium, and make small "patch" updates by updating the -<element> of the specific selenium version we are going against.

Selenium follows semver, and the docker-selenium does its best with what we have. if you have a better alternative, feel free to file a PR. if not, then this process is not going to change unless you provide some sort of valid explanation / reasoning / alternative.

[cypherfunc]

Selenium does not follow semver at all.
SeleniumHQ/selenium@8c9d018#commitcomment-32222018