2008/10/23 Hannes Magnusson <[EMAIL PROTECTED]>: > On Thu, Oct 23, 2008 at 12:26, Jani Taskinen <[EMAIL PROTECTED]> wrote: >> Hannes Magnusson wrote: >>> >>> On Thu, Oct 23, 2008 at 11:51, Jani Taskinen <[EMAIL PROTECTED]> wrote: >>>> >>>> 2. You can always simply put a short comment like "Fixed in CVS, needs >>>> documenting" and reclassify the bug report as docu issue. There's no need >>>> for some fancy shortcuts or such. Just tune your process.. >>> >>> Well, or use the [DOC] tag in commits. >> >> s/or/and/ >> >>> Since the [DOC] tag failed so miserably I can't imagine people would >>> bother reclassifying the report either, unless the system forces them >>> to do so. >> >> Just needs advertizing. You can't force anything.. > > Ok... How about new quickfix option then, "Fixed in CVS - needs docs" > and introduce new status "NeedDocs", which that quickfix option would > change the status to? > Then docwriters can simply search for that status (including correct > categories, if they are only comfortable documented specific exts) and > properly close the report ones fixed. > > I would however very much appreciated if developer would write an > example in the description field and/or explain the change with a link > to the CVS commit, but I fear that is way to much to ask for. > > -Hannes
It shouldn't be too hard for an example as I'm _sure_ the devs test the fixes with PHP code to make sure it is a good fix? So just a cut and a paste of the PHP code should be enough! -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
