another release soon?

There's a few bug fixes currently in SVN that combined probably justify a 
release.  There's one task on the todo list, "Cache components in 
per-request fast memory cache when !static_source_mode", marked as being 
for 1.32, but I don't know if this has been started.

So any objections to a new release?  If not, should it just be 1.32?  I'm 
inclined to just increment the minor version by 0.01 per release at this 
point, and maybe if we ever do big re-architecting like we did for 1.10, 
we can just call that 2.0 (and maybe even just release it under a Mason2 
namespace, for that matter).


-dave

/*===================================================
VegGuide.Org                        www.BookIRead.com
Your guide to all that's veg.       My book blog
===================================================*/


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click