[lively-kernel] trac and Lively issue worlds
jens.lincke at hpi.uni-potsdam.de
Fri Nov 11 11:12:23 CET 2011
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.
PS: The colors are so squeaky :-)
On 11.11.2011, at 00:38, Lauritz Thamsen wrote:
> 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? :-)
> On Nov 4, 2011, at 10:40 AM, Lauritz Thamsen wrote:
>> 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!
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lively-kernel