Most of the apps follow their versions / branches inline with that of Frappe to help users to install compatible versions.
However I noticed that apps like
have only main and develop branches, from which user won’t able to get that which Frappe version should be used for these apps.
Should not there branches corresponding to that of Frappe?
The main branch is released weekly, providing a stable version. However, the develop branch is updated regularly, with changes made daily. If you want to stay updated with the daily version, you can install the develop branch. For a more stable version, use the main branch.
Thank you for your prompt reply.
But doubt is that will these Apps work on Frappe 16, 15, 14, 13 and 12 versions i.e these apps are insensitive to Frappe Versions and so work on any version of Frappe or they demand 1 or 2 specific versions of Frapee?
App running on version 15 and above.
From the department “Reverse engineering info presented in a rather dispersed form in order to make sens of it and understand the links” ( 
):
On Github there are:
Versions are specific branches. They come as “version-”, and there are “hotfix” variants.
Commits are listed for the user, in the installed apps list, of a site on Frappe Cloud, so I’d say they seem to be quite relevant for precise identification.
Tags are probably used in automatic regular generating templates for Dockerfiles, Helm and such.
What works with what, that’s a tricky question. There doesn’t seem to be an official list of these. Also, there seems to be no “revoke-app” (due to security or other issues) info hub, with “rather use this commit”.
What’s your use-case/need/painpoint for this kind of info?
Do you feel that this is time to have Frappe Package (or App) Manager which can handle dependencies, select the right version of App for your Frappe installed?
Yes, I already thought about such a thing myself.
The difficult part is getting the data, because it changes all the time, with each bug, commit, tag, update, CVM, newly discovered incompatibilities.
It’s not easy for anybody to find bugs, because bugs are not generally self-evident and can be discovered at any time by anybody, and each time some adaptation of the dependencies list is necessary. And what about backporting?
A list of “what works with what” means: multiple app-to-app edges, there might be quite many of them, especially if you also want to include all the marketplace apps, and even external apps. In other words, any combination of these.
It also implies easy updating after any update of such a list. Otherwise, the use is limited anyway. But for whom is that easy – at least at the beginning, and especially for self-hosters --, data transfers etc. included?
Though I am lucky that this post got nice responses, but still unable to get the answer.
Looks no one from the team of CRM, helpdesk, print_designer is active on this forum or Frappe has no guidelines / good practices for its teams and projects.
Well, there was a slow forum week, but wasn’t there also a week of public holidays in India (at least that’s what my lookup found)?
Or maybe they did an offsite reset week, an after-conf decompression and (I’d suggest: well earned) recharge time?