On Fri, Oct 7, 2016 at 4:42 PM, Pavel Raiskup praiskup@redhat.com wrote:
SSIA, WDYT?
I'm ++, /me hates all that struggling with RHBZ.
On Friday, October 7, 2016 5:17:20 PM CEST Igor Gnatenko wrote:
On Fri, Oct 7, 2016 at 4:42 PM, Pavel Raiskup praiskup@redhat.com wrote:
SSIA, WDYT?
I'm ++, /me hates all that struggling with RHBZ.
I like bugzilla, but for upstream project I wouldn't bother other source consumers with doing Red Hat Bugzilla accounts..
While we discuss bugzilla -- it would be fine to have direct link to list of (all) bugs currently filled against Copr, somewhere. That's imo the major benefit of github issues for newcommers (no need to search how the component or project is named .. the list is there).
Thanks, Pavel
Dne 7.10.2016 v 18:17 Pavel Raiskup napsal(a):
While we discuss bugzilla -- it would be fine to have direct link to list of (all) bugs currently filled against Copr, somewhere. That's imo the major benefit of github issues for newcommers (no need to search how the component or project is named .. the list is there).
Great idea. Done. https://github.com/fedora-copr/copr/commit/f55f3a959646d82640fbb7fa613b5001e...
Dne 7.10.2016 v 17:17 Igor Gnatenko napsal(a):
I'm ++, /me hates all that struggling with RHBZ.
I'm --, I hate github's issue tracker when it is longer than one page. It is useful for small project. But for bigger projects no. BZ allows us to track which issues were modified, and which are part of which release. We can change several reports at once. I am using the reporting charts...
On Mon, Oct 10, 2016 at 9:32 AM, Miroslav Suchý msuchy@redhat.com wrote:
Dne 7.10.2016 v 17:17 Igor Gnatenko napsal(a):
I'm ++, /me hates all that struggling with RHBZ.
I'm --, I hate github's issue tracker when it is longer than one page. It is useful for small project. But for bigger projects no.
Then why for systemd it works fine?
BZ allows us to track which issues were modified, and which are part of which release. We can change several reports at once. I am using the reporting charts...
You can use it with github as well. For example, systemd team does: https://in.waw.pl/~zbyszek/blog/how-is-systemd-doing-on-github.html
-- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On Mon, Oct 10, 2016 at 09:35:59AM +0200, Igor Gnatenko wrote:
On Mon, Oct 10, 2016 at 9:32 AM, Miroslav Suchý msuchy@redhat.com wrote:
Dne 7.10.2016 v 17:17 Igor Gnatenko napsal(a):
I'm ++, /me hates all that struggling with RHBZ.
I'm --, I hate github's issue tracker when it is longer than one page. It is useful for small project. But for bigger projects no.
Then why for systemd it works fine?
Different people different taste?
Pierre
On Mon, Oct 10, 2016 at 9:44 AM, Pierre-Yves Chibon pingou@pingoured.fr wrote:
On Mon, Oct 10, 2016 at 09:35:59AM +0200, Igor Gnatenko wrote:
On Mon, Oct 10, 2016 at 9:32 AM, Miroslav Suchý msuchy@redhat.com wrote:
Dne 7.10.2016 v 17:17 Igor Gnatenko napsal(a):
I'm ++, /me hates all that struggling with RHBZ.
I'm --, I hate github's issue tracker when it is longer than one page. It is useful for small project. But for bigger projects no.
Then why for systemd it works fine?
Different people different taste?
Comment was about small/big projects.
Pierre _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
copr-devel@lists.fedorahosted.org
-
Igor Gnatenko -
Miroslav Suchý -
Pavel Raiskup -
Pierre-Yves Chibon