On 24 June 2015 at 14:46, Luigi Toscano <[email protected]> wrote: > On Wednesday 24 of June 2015 14:32:23 Jaroslaw Staniek wrote: >> Hi, >> Bugzilla with all its issues was a bit customized for our needs and >> had a workflow familiar for average user of KDE software and services. >> As we're heading to a switch to the Phabricator Maniphest [1] (so far >> the support from our Sysadmin Team is great!), I'd like to hear >> opinions and ideas how it can be made wrapped into something trivial >> to use. > > I don't have ideas for Phabricator as I couldn't play with it so far. But just > to be clear "we" as Calligra or "we" as KDE? In both cases, I thought that we > were going to evaluate first, and in any case the bug handling part was not in > the center of the discussion for now (more focus on code review, tasks, but > not bugs for now - not before result reports and migration plans I haven't > seen at all around).
We as KDE :) I know my question comes early and the scope of use of Phab isn't finally decided. But I believe it would be most efficient to keep a bug database in one system. Certainly bugs translate to tasks in a typical workflow. -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
