there's no reason to tag and release versions if the answer to any issue is 'make current', and support is not available unless that's been done.  Far better to either have meaningful releases with  stable and devel branches, or not to have releases at all.

Well, the response on a stable version about a bug report that's been already fixed would be: "apply this patch and retest, come back to us if problem persists"

Isn't that exactly what make current does?

This way of developing may be not broken-trunk-proof, but from your comment I think an easier way to approach Lon's suggestion would be making a more understandable way for simple users (not fs devs) to check what modules have been altered from their version to the latest, in order to check if an issue has been solved or not, as of those clients that only want "released versions", that's the hard part.

ps: hmmm Anthony's message makes my post outdated but i spent a lil bit of thought on it so i post anyways ^^

-Milena