<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, Lauritz<div><br></div><div>thanks for putting it together. I think it pretty much describes the process how it worked since we use trac.</div><div>We should add some information how you can get the revision number that fixed the bug, e.g. version info of the module.</div><div>I really long for something like CodeDB so that we can get change messages in our code again as we have now for the Parts.</div><div><br></div><div>Best,</div><div>Jens</div><div><br></div><div>PS: The colors are so squeaky :-)</div><div> </div><div><div><div>On 11.11.2011, at 00:38, Lauritz Thamsen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi.<div><br></div><div><a href="http://lively-kernel.org/trac">Our trac instance</a> and <a href="http://www.lively-kernel.org/repository/webwerkstatt/issues/">Lively's issues folder</a> have been fairly active; and Lively Kernel as well: we fixed a couple of critical issues in the last week!</div><div><br></div><div>Our ideas on using trac and Lively can be found here: <a href="http://www.lively-kernel.org/repository/webwerkstatt/projects/LivelyKernel/process.xhtml">http://www.lively-kernel.org/repository/webwerkstatt/projects/LivelyKernel/process.xhtml</a></div><div>Any feedback? :-)</div><div><br></div><div>Best,</div><div>Lauritz</div><div><br><div><div>On Nov 4, 2011, at 10:40 AM, Lauritz Thamsen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi.<br><br></div><div>In the last week we started to use <a href="http://lively-kernel.org/trac">Lively's trac</a> again. There, we keep track of <a href="http://lively-kernel.org/trac/report/11">existing issues</a>, <a href="http://lively-kernel.org/trac/report/12">feature requests</a> and <a href="http://lively-kernel.org/trac/report/14">necessary refactorings</a>. </div><div><br></div><div>Besides trac we also use Lively itself for <a href="http://lively-kernel.org/repository/webwerkstatt/issues/">issue reports</a>. Whenever there's a bug that's description isn't absolutely trivial, it's a great help to have a small example in Lively for the issue. Such issue pages are usual Lively worlds and, therefore, can contain any morphs and texts that help to understand and reproduce issues. Examples: <a href="http://lively-kernel.org/repository/webwerkstatt/issues/111017_StaticBindingOfSuperInClosures.xhtml">http://lively-kernel.org/repository/webwerkstatt/issues/111017_StaticBindingOfSuperInClosures.xhtml</a>, <a href="http://lively-kernel.org/repository/webwerkstatt/issues/111026_CustomFormattedBinsInPartsBin.xhtml">http://lively-kernel.org/repository/webwerkstatt/issues/111026_CustomFormattedBinsInPartsBin.xhtml</a></div><br><div>We create such issue worlds from a template: <a href="http://lively-kernel.org/repository/webwerkstatt/issues/CreateIssuePage.xhtml">http://lively-kernel.org/repository/webwerkstatt/issues/CreateIssuePage.xhtml</a>.<br><br>Please feel free to contribute!<br><br>Best,<br>Lauritz</div></div></blockquote></div><br></div></div>_______________________________________________<br>lively-kernel mailing list<br><a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br>http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel<br></blockquote></div><br></div></body></html>