Trinity's release model

After upgrading to 3.5.13.1 and getting a bunch of new bugs introduced I started thinking it might be a good idea to release new packages continously as changes are made to the code, instead of doing a big release once every few months. I realize there are some major changes going on in the code and they cannot be released partially. Still I think that thanks to git's branching and merging capabilities it should be possible to merge some smaller changes and bugfixes into master and release them as update. Woludn't that be an easier way to track new bugs introduced to the code? Instead of getting a whole load of bug reports after a major release, bugs would be reported as they appear and would be easier to track down to conrete packages and changes made in the code. Janek