Scenarios to orient and test our versioning scheme, in presumed order of importance.

1. New MediaWiki minor (e.g. v1.41.0) and patch release (e.g. 1.40.1 and v1.41.1)
2. New WikiMedia Extension release which is versioned, or otherwise we surmise, as major, minor, or patch releases (including new features the Suite team builds directly, which most likely happen in an extension as well)
3. Changes in /example
4. An update or change of an underlying Docker dependency in an image we publish

I think the working assumption for this initial conversation should be that we maintain a single versioning scheme for the entire WikiBase Suite, releasing all images at the same time.

If in the course of this discussion we can also evaluate whether independently versioning and releasing /example and/or each image seems critical or inevitable, and, if so, design the unified versioning with awareness of this trajectory.

from one of the last conversation this is the state if this:

@roti_WMDE will prepare visual aids to support and lead the conversation
@darthmon_wmde will schedule the call coordinating with @roti_WMDE

timeline: the next 1-2 weeks

Sketch from @RickiJay-WMDE and my discussion about the scheme today:

https://www.tldraw.com/r/HAjKRS4O9Szr6d85StAT4?v=440,-494,2626,1402&p=page

Decisions made and AC:

• decision on a versioning scheme

shown in the diagram above

• decision on the number to start with

since we are now on wmde.20 and aiming to follow the logic and making it intuitive we have decided to start from 20.0.0