...
| Name | Releases Count | ||
|---|---|---|---|
| In-Portal | 80 | ||
| Modules | |||
| In-Link | 74 | ||
| In-News | 70 | ||
| In-Bulletin | 74 | ||
| In-Commerce | 69 | ||
| Custom | 43 | ||
| Themes | |||
| Default | 35 | ||
| Simple | 34 | ||
| Advanced | 43 | ||
...
Definitely such version madness can't be continued any longer.
Solution
- 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)
- 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:
- if it wouldn't then update In-Portal version constrain for that module
- if it would then maybe try to figure out minimal module version with which that module can work