I think that is a good idea to provide information about this, I have a branch at lp:~mvo/click/frameworks.json that adds the information about deprecated/current/devel to the frameworks. Extending the branch to list that is simple enough. One open question for me is where the information about deprecated/supported/devel should life. It seems we can store it in the package or make it part of a webservice that we can update in a more dynamic fashion. If updates via sru are good enough, then this is not needed.
I think that is a good idea to provide information about this, I have a branch at lp:~mvo/click/frameworks.json that adds the information about deprecated/ current/ devel to the frameworks. Extending the branch to list that is simple enough. One open question for me is where the information about deprecated/ supported/ devel should life. It seems we can store it in the package or make it part of a webservice that we can update in a more dynamic fashion. If updates via sru are good enough, then this is not needed.