> In my personal opinion, it is time that we should start planning a new > release. My personal opinion is that we should get out a 3.2.1 release > candidate out soon (after fixing some bugs and adding some enhancements in > jira, e.g. TORQUE-56 and TORQUE-54), and then start progress towards a 4.0 > release whith major changes (chucking out the village library etc.) +1
> Any thoughts ? I was browsing the issues in Jira and noticed that quite a few major one are actually Village related. Seems like a "psuedo-component" for Village might make identifying these much easier. (so they can be block resolved with 4.0...lol). I've been meaning to get back to Torque-50 (Add-on support) and look at what Thomas suggested (and may have already implimented). Of course, I'll sign up for any work needed for Torque-54 - 8) If there's time, I might take a wack at Torque-27 (DB specific options) by adding support for a <OPTION key=.. value=> XML element that was talked about in an dev e-mail thread a while back. This would require a change to the DTD to add it, any problems with that? Let me know if I can help on any other issues, docs, etc. Greg Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
