For some of my plugins (e.g. questionnaire), I maintain multiple release trees. My strategy is this:
- New features go into the next release of Moodle. So, if current release is 3.5, I create new features for the 3.6 release until the 3.6 is current.
- Bug fixes, security fixes, and valuable improvements (my decision), go into the current release and backported up to two previous releases.
When I can, I like to make a given release tree available to other release trees. So, for example, I have made my 3.5 release available to 3.6 (until new features are ready), 3.4 and 3.3. This allows the users of questionnaire to have the latest bug, security and improvement features without adding new features. When they want the new features, they simply need to move ahead one release.
The problem I am having is that the plugins database
always displays the highest release available for all of the release it supports. So, for example, I just released a new version of the 3.5 and the 3.4 release tree. The 3.5 release supports 3.6, 3.5, 3.4 and 3.3. The 3.4 release supports 3.4 and 3.3. On the plugins page, the new 3.5 release shows clearly at the top. The next one below that is for 3.2. I have to scroll down through all of the rest of the release trees (3.1 right down through 1.9) before I find the 3.4 release.
I believe this is because two of the releases support 3.4. Is there a way I can have more control over the order the releases are displayed? Or, could we set the order to be based on release date?