21:44 < killes> Dries_: please remove all releases older than 4.5, all non-4.7 RCs
+1
What to do with the issues associated with those releases?
Change the release to 4.5 for all pre-4.5 releases. I assume there will be a comment added to the issue recording the change.
Create a new release called "obsolete" (or some other obnoxious but creative name) and assign anything that is now pre 4.5 to be against it so we know this is old stuff if we need to know, and it does not get in the way later. One related issue: any issue that says "cvs" now and does not get fixed, remains as cvs even if we release 4.7, then 4.8 then 5.0, then 5.1, ...etc. Later someone has to go thru and mark some of them as no longer applicable, ...etc. Is there a better way of doing this? For example, all current issues are marked either "4.6" or "pre-4.7". Future ones become "4.7" if they are against that live branch, or "pre-4.8". Would this ease tracking of old issue and give a sense of how long they have been around (since how many releases, not number of days).