Personally, I dont't care what issue tracking tool we use, as long as it can
visualize the issues as a Kanbanboard. Github issues + labels like "planning",
"to develop", "developing", "to test", "testing", "to release" and "released"
(or whatever workflow might fit owncloud development) + huboard.com can be used
to create a simple kanban tool.
I'd love to give a pecha kucha at the developer meeting on how kanban would
help make the owncloud development more transparent and let developers decide
on what to tackle next or where help is needed. Let me know if you are
interested! Then I'll prepare it on the trip to Berlin.
Unfortunately, I'll not arrive before Saturday evening and would also like to
help Tom give a demo of the automated cucumber testsuide we started to work on.
But since results are going to be presented on sunday this should work out fine.
So long & happy to see you all in a few days!
Jörn
"Thomas Müller" <[email protected]> schrieb:
>We will define this in Berlin next weekend.
>
>Tom
>
>Mark Ziegler <[email protected]> schrieb:
>
>>Hi,
>>
>>still have to ask some simple questions regarding new bt.
>>
>>When reporting a bug there is no category like bug, feature request or
>enhancement.
>>Should we use it for all three kinds, not only bugs?
>>
>>Cheers,
>>Mark
>>_______________________________________________
>>Owncloud mailing list
>>[email protected]
>>https://mail.kde.org/mailman/listinfo/owncloud
>_______________________________________________
>Owncloud mailing list
>[email protected]
>https://mail.kde.org/mailman/listinfo/owncloud
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
