> Maybe, but they don't make easy bedtime reading - they're just lists
> of bugfixes and enhancements.

Lol, no, not bedtime reading, but as someone who's been using the
branch forever, I ( and I shit you not ) check those two links every
morning in the 10 minutes while I wait for my carpool as well as skim
through the digest from this group.  It helps keep me up to date and
doesn't take much time.  As an incredibly useful tool that helps me
make a living it's a minimal bit of effort on my part.  Is it always
obvious? Not always, but the commit comments are generally pretty damn
good.  Do I wish there was a nicely formatted, document outlining the
changes, fixes, deprecations and todo list of things that take me by
the hand so I don't have to think? Sure, would make my life easier
still, but I don't expect it in the slightest as I can get that from
the two links I've posted and more specific deprecation information
from http://api.cakephp.org/1.2/deprecated.html

When the trunk is updated there has been an announcement made here on
the list as well as the bakery.  The latest announcement, a link to
which is posted here and on the main page of the cakephp site, deals
specifically with the issue that spawned this thread in the 2nd
paragraph.  There is no inference needed for that, it's laid out quite
plainly I think.

I'm sorry, maybe I don't understand what you think "release notes"
should be.  Maybe you need to explain what it is you think release
notes should be, without duplicating the information already being put
out by the devs.

Maybe I'm a fan boy, maybe I've just been using Cake for so long that
it mostly all makes sense to me.  I dunno. I'm hungry.  :/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to