On 01/04/2012 12:32 AM, Andrey Ivanov wrote:

Bugzilla will not be used any more (at all)?

It will still be used for some things. Some people will enter bugs into the system by filing a bug against Fedora or Fedora EPEL for the particular component of 389 in that release (e.g. Fedora -> 389-ds-base or Fedora EPEL -> 389-admin). The development team will then triage the bug to see if it affects the upstream 389, and will copy the bug into a trac ticket. The old bugs filed against Product: 389 will still be in bugzilla.

Is there any reason for that?

We need a separation between "upstream" 389 development and "downstream" Red Hat processes. It has become too confusing to keep the "upstream" development separated from the "downstream" process in the same bugzilla tool. Almost all of the other related projects (freeipa, sssd, dogtag, others) have moved to using their fedorahosted.org trac for keeping track of bugs/enhancements/tasks.

Will the old tickets be transferred to Trac?

Some of them, mostly the ones that are still open, and they will also still be available in bugzilla. We have an internal tool for linking bugzilla bugs to trac, so we can manage the bugzilla bug/trac ticket lifecycle easily. The old closed/verified bugs will not be moved to trac, they will be available in bugzilla.

Thanks!

2012/1/4 Rich Megginson <rmeggins@redhat.com>

From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Tuesday, January 03, 2012 3:42 PM
To: General discussion list for the 389 Directory server project.
Cc: Groten, Ryan
Subject: Re: [389-users] bak2db restore got stuck in infinite loop

I've filed https://fedorahosted.org/389/ticket/4 to track this issue. Please feel free to add yourself to the CC list (you'll need a Fedora account to do so - see https://fedorahosted.org/389/wiki) and add any comment
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users