Another good example that lacks documentation is behavior
additions/changes. I.e.: the patch for has_one saving on create versus
saving on update where it used to save on both. The new patch doesn't
do what I expect and I has to bug poor Jonathan to clarify what his
expectations were on his patch (which he humored me and explained; thanks!).
Kevin Clark wrote:
I think at the moment it's heavily encouraged that documenation be
included with patches. What this turns out to mean commit side is that
if your patch has associated documentation and tests included it's
significantly more likely that it will be commited. More people just
need to know this (or take it seriously).
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
