Well, I appreciate the non-commercial environment of cake development and the it-would-be-done-if-only-someone-would-volunteer-to-do-it approach. I don't have an argument with that. I just want to see the release notes that I was referred to by Mariano Iglesias who sadly has not yet revealed his source.
A lot of stuff in trac is chaff that doesn't affect day-to-day cake, but as chaff it serves to obscure the important need to know changes. Maybe there is some way of better detailing these changes in the comments added to each code change? On 18 Juny, 16:26, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > On Wed, Jun 18, 2008 at 10:09 AM, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > >https://trac.cakephp.org/timeline > >https://trac.cakephp.org/wiki/changelog/1.2.x.x > > > All I've ever needed, all I've ever used :D > > As loath as I am to argue with people (that's a joke, for those who > don't know me) I have to agree that sometimes, it would be nice to see > documentation with the releases that says "we've added this cool new > feature, and here's how to use it." > > Given the massive size of the change log, I don't know if that's even > feasible. > -- > Chris Hartjes > Internet Loudmouth > Motto for 2008: "Moving from herding elephants to handling snakes..." > @TheKeyBoard:http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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?hl=en -~----------~----~----~----~------~----~------~--~---
