Will the QuickForm API always be a moving target?

I just upgraded from Quickform 3.0 to 3.1 on my development machine and I am finding that Quickform 3.1 is throwing E_USER_ERROR level errors for depreciated methods. I read here: http://marc.theaimsgroup.com/?l=pear-general&m=105890947805091&w=2 that at least one depreciated method is to be removed. Will other methods also be depreciated? It would be helpful to see a list. I have been using QuickForm extensively since version 2.2. Thanks to everyone who has worked on it-- what a great component! Because I have been using Quickform for so long it is a little concerning to grep through my source tree and see how often I have used methods which are now depreciated. I have been trying my best to always use the most recent version but I am finding that upgrading QuickForm is like playing with fire. Every upgrade since 2.9 has broken my code. I'd really love to see the api freeze up a bit-- production environments need this kind of stability. The api also seems to be getting increasingly complex. As the source gets heavier and heavier QuickForm might be in darger of no longer being so quick ;) I personally do not use the renderer stuff at all-- 2.10 had all the features I need. I suppose I could maintain a personal version of 2.10 but I would prefer to stay in line with the main trunk. I hope this is not taken in the wrong way. I really do appreciate all the work put into Quickform. culley