Hi,

Current Boostrap version is 3.2.0, so my proposal is to make a version of a Bootstrap Theme of 7.x-3.2.0-dev and develop it into 3.2.0.1, 3.2.0.2, 3.2.0.N which have the same Bootstrap framework requirement. If that is not Drupal'ish versioning - 3.20-dev, 3.20.1, 3.20.2, 3.20.N could be also an option.

Why? Because there are projects, which get started using framework 3.0.0 and then stable Drupal Bootstap Theme, but then the requirement for the latest stable theme becomes 3.1.0, 3.2.0 and so on - then it is easy to get lost in compatibility problems.

There will be more releases, but much easier to understand what version of theme is built on which framework version with all their features and shortcomings.

Comments

markhalliwell’s picture

markhalliwell
Primary language English
commented
Status: Active » Closed (won't fix)
Related issues: +#2311991: [bootstrap][policy] Figure out versioning

Unfortunately this isn't possible. The limitation is in how drupal.org packages it's modules/themes. It only allows for CORE_VERSION.x-MAJOR.MINOR and that is it. It doesn't allow semantic versioning whatsoever. They are putting in semantic versioning/packaging for core, but I do not believe contrib will get that (especially any existing 7.x stuff).

Also, we're aware that there is "inconsistencies" between the Drupal base theme "Bootstrap" and the external framework "Bootstrap" version... please see the related issue. There really just isn't an easy solution for this.

markhalliwell’s picture

markhalliwell
Primary language English
commented

Furthermore, if a security related issue arises (which one has) it must be a separate release (doesn't include any other code changes/features). Because we're trying to keep parity with the major version (3), this limits us to only incrementing the minor version.

So while I have been planning on releasing all the bug fixes and new features in 7.x-3.1, this will likely be the security release and we'll have to go with 7.x-3.2 instead.