Child pages
  • [install] Module version dependency problem [5.3.0-B1]
Skip to end of metadata
Go to start of metadata

This is current release count for each module/theme in In-Portal repository:

NameReleases Count
In-Portal80
Modules
In-Link74
In-News70
In-Bulletin74
In-Commerce69
Custom43
Themes
Default35
Simple34
Advanced43

If looking closely, then some facts can be easily noticed:

  • module release count is almost identical
  • theme release count is almost identical
  • module release count is almost identical to in-portal release count

This is no mere coincidence unfortunately, but a way to keep track of which module/theme is compatible with which In-Portal version by releasing them at the same time. As a side effect of this we're forced to release a version with no changes at all to keep version number increased.

Definitely such version madness can't be continued any longer.

Solution

  1. instead of specifying exact module dependencies (e.g. 5.2.1) we need to specify version constraint (e.g. ~5.2.1 which means any "5.2.*" version larger and including 5.2.1)
  2. locate all JIRA issues, that has more then 1 commit (would usually mean commit to In-Portal and other module) and see if change made to module would work without change made to In-Portal:
    1. if it wouldn't then update In-Portal version constrain for that module
    2. if it would then maybe try to figure out minimal module version with which that module can work

Related Tasks