<div dir="ltr">I would like a bug tool integrated into Squeak and per Monticello package. <div style>Could we use Monticello somehow to to report and track bugs ?</div><div style><br></div><div style>Karl</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sat, Feb 23, 2013 at 7:12 AM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</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"><br>
On 22-02-2013, at 8:50 PM, Colin Putney <<a href="mailto:colin@wiresong.com">colin@wiresong.com</a>> wrote:<br>
><br>
> The Inbox is meant for changes that need review—either contributions from developers without direct access to the trunk, or from core developers that would like a second set of eyes on the code before it goes into trunk.<br>
<br>
</div>I really wish we had enough available eyeballs to review everything. I suggest that the most careful review is required for the sort of changes that 'core developers' produce. If nothing else it is a way to reduce the truck-factor and make sure that things are explained well enough for someone not heavily involved in the original work to be able to understand what is being done.<br>
<div class="im"><br>
<br>
> So, sure, a Mantis entry is great, but core developers putting stuff in the Inbox ought to be fairly rare. The idea is to keep it easy to contribute, with minimal ceremony.<br>
<br>
</div>No ceremony at all worries me. Call me Captain Slow (cf James May) but I like procedures. They're recipes for maintaining sanity over time.<br>
<div class="im"><br>
<br>
tim<br>
--<br>
tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
</div>Is reading in the bathroom considered Multi-Tasking?<br>
<br>
<br>
<br>
</blockquote></div><br></div>