<br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 10:31 AM, Russell Bryant <span dir="ltr"><<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/04/2013 12:03 PM, Daniel P. Berrange wrote:<br>
> On Mon, Mar 04, 2013 at 08:55:25AM -0800, Dan Wendlandt wrote:<br>
>> Yeah, I agree. Too often TODOs are put there just to tell reviewers that<br>
>> you are doing something short-sighted, but that you recognize it. Really<br>
>> reviewers should be enforcing that there is a bug to track that item, or<br>
>> requiring it to just be done in the initial version. There is also a use<br>
>> of a TODO which I would probably refer to as a "FUTURE" tag, which is to<br>
>> say: someday, we may plan on implementing X, and if we do that, the change<br>
>> would go here. One could argue that those are useful comments to have in<br>
>> the code, but do not require bugs, as they do not actually represent<br>
>> deficiencies that could currently be fixed. Perhaps we should use<br>
>> something other than TODO in that scenario.<br>
><br>
> Personally I've always used "XXXX" or "FIXME" to indicate gross hacks that<br>
> should be fixed asap, and "TODO" for the random ideas that might be interesting<br>
> to explore in the future. So if we want to track bugs, then perhaps we could<br>
> use "FIXME bug 34242" for that purpose, and leave "TODO" for ad-hoc thoughts ?<br>
<br>
</div>+1<br></blockquote><div><br></div><div>I'm happy with that approach.</div><div><br></div><div>dan</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Russell Bryant<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div>