Actually, I think it would be a great thing if for products that are not 'fully active' anymore, one of the engineers at ST would - once a month - check the bug-reports and apply all the 'easy fixes' (such as typo-corrections, and obvious things like the above mentioned issue).
By 'easy fixes', I mean things that do not require following complex code or investigating things in deep levels.
-Then once every third month, some of the complicated stuff could be taken.
The 'once-a-month' is not meant just for one particular product, it's more like "what could be done quickly today?".
I know that most of the engineers are working on the leading-edge stuff and their thoughts are occupied with these new products, which is why I'd only ask for a 'once-a-month' event (eg. right before starting "new tasks").
OT: ... Personally, using some kind of version control is a good habit in my opinion. I picked git over SVN, because I have worked with (the obviously flawed) CVS for several years. When I decided to move to something different and tried checking out a SVN project, the filenames were messed up (truncated and casing problems), so I decided to try git and have grown quite fond of it. It does take some getting used to in the beginning, but after a while, it's just another habit. ;)
