Hi Walker, CakePHP is lucky enough not to have too many security concerns to date. That does not mean they wont arise. For the Rails guys, I can understand their apprehension in completely divulging the source of their security concerns. With something surrounded by so much hype as Rails, its just a perfect opportunity for a hacker to take their warnings and exploit the system.
Ideally, we could operate with full information all the time. The problem is this is not a reality. For example, we announce updates via the google group, but not everyone who is using Cake receives email; or they receive abridged or digest emails, meaning they may never hear about updates. Some time later they will go to cakeforge or the google group site. Maybe those people not receiving emails use the rss feeds. But for us its hard to know how well the information gets disseminated. I can only imagine the Rails team has similar concerns. We are as open as we can be and the majority of the time there is someone from the CakePHP team in the IRC channel to provide more information when needed. We are continually talk about everything going on with Cake over IRC. We recommend people read the irc logs too because they contain a plethora of information. keep lurking and get baking. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
