#166 pagure issues or RHBZ?
Closed 4 years ago Opened 4 years ago by alick.

It seems that both pagure issues and RHBZ are used for bug reports, which doesn't sound good.

If we're going to stick with pagure issues, we need to replace the bug reporting links to pagure from RHBZ. And somehow redirect future reports to RHBZ to pagure.

If we're going to stick with RHBZ, we probably should disallow new pagure issues. Then it's better to create a 'docs' component in RHBZ for Copr for documentation issues.

If we want both, then please assign different subtopics to each, and make it clear in README.


Hello,

we allow both issue trackers - RHBZ and pagure issues. RHBZ is more oriented to concrete production problems with copr.fedorainfracloud.org whereas Pagure issues are more oriented to RFEs and rather generic bugs that represent a problem but they do not block a use-case of certain team using COPR Fedora instance, there is a workaround etc.

It's mirroring our situation that we:

1) develop a generic RPM build system (Pagure Issues)
2) take care of the most prominent instance, which is the Fedora one at the moment. (RHBZ)

Now, I agree this might be a bit confusing e.g. when a user looks for an issue if it has been already reported or not. We will see if we can make the situation any better.

So, how about we say in README:

  • report bugs of the Fedora Copr Instance to RHBZ
  • report bugs of current copr code to Pagure Issues
    ?

Besides, it would be better to rename Copr in RHBZ to something like Fedora
Copr Instance. But not sure if that's possible with associating existing
RHBZ bug reports for Copr?

Regards,
Alick

On Thu, Nov 9, 2017 at 3:09 AM, clime pagure@pagure.io wrote:

clime added a new comment to an issue you are following:
``
Hello,

we allow both issue trackers - RHBZ and pagure issues. RHBZ is more
oriented to concrete production problems with copr.fedorainfracloud.org
whereas Pagure issues are more oriented to RFEs and rather generic bugs
that represent a problem but they do not block a use-case of certain team
using COPR Fedora instance, there is a workaround etc.

It's mirroring our situation that we:

1) develop a generic RPM build system (Pagure Issues)
2) take care of the most prominent instance, which is the Fedora one at
the moment. (RHBZ)

Now, I agree this might be a bit confusing e.g. when a user looks for an
issue if it has been already reported or not. We will see if we can make
the situation any better.
``

To reply, visit the link below or just reply to this email
https://pagure.io/copr/copr/issue/166

Metadata Update from @alick:
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata