[lively-kernel] trac and Lively issue worlds

[Lauritz Thamsen]

Hi Jens.

Thanks for your feedback!

> We should add some information how you can get the revision number that fixed the bug, e.g. version info of the module.

I think it's okay to just save the head revision number after fixing a bug - with auto-commit and without commit messages, most fixes aren't a single commit anyway. I added some description to the process world and another morph to the issue template - it lets you conveniently save the current head revision on the issue page.

And I absolutely agree that we do need meaningful commits and messages soon...so looking forward to CodeDB! :-)

Best,
Lauritz

> PS:  The colors are so squeaky :-)
Feel free to change... ;-)

On Nov 11, 2011, at 2:12 AM, Jens Lincke wrote:

> Hi, Lauritz
> 
> thanks for putting it together. I think it pretty much describes the process how it worked since we use trac.
> We should add some information how you can get the revision number that fixed the bug, e.g. version info of the module.
> 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.
> 
> Best,
> Jens
> 
> PS:  The colors are so squeaky :-)
>  
> On 11.11.2011, at 00:38, Lauritz Thamsen wrote:
> 
>> Hi.
>> 
>> Our trac instance and Lively's issues folder have been fairly active; and Lively Kernel as well: we fixed a couple of critical issues in the last week!
>> 
>> Our ideas on using trac and Lively can be found here: http://www.lively-kernel.org/repository/webwerkstatt/projects/LivelyKernel/process.xhtml
>> Any feedback? :-)
>> 
>> Best,
>> Lauritz
>> 
>> On Nov 4, 2011, at 10:40 AM, Lauritz Thamsen wrote:
>> 
>>> Hi.
>>> 
>>> In the last week we started to use Lively's trac again. There, we keep track of existing issues, feature requests and necessary refactorings. 
>>> 
>>> Besides trac we also use Lively itself for issue reports. 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: http://lively-kernel.org/repository/webwerkstatt/issues/111017_StaticBindingOfSuperInClosures.xhtml, http://lively-kernel.org/repository/webwerkstatt/issues/111026_CustomFormattedBinsInPartsBin.xhtml
>>> 
>>> We create such issue worlds from a template: http://lively-kernel.org/repository/webwerkstatt/issues/CreateIssuePage.xhtml.
>>> 
>>> Please feel free to contribute!
>>> 
>>> Best,
>>> Lauritz
>> 
>> _______________________________________________
>> lively-kernel mailing list
>> lively-kernel at hpi.uni-potsdam.de
>> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hpi.uni-potsdam.de/archive/lively-kernel/attachments/20111111/bab5354c/attachment.html>