[Automatic Bug Reporting Tool - ABRT] #919: don't reply with KNOWN response for reports connected to BZ which has been closed because of EOL
#919: don't reply with KNOWN response for reports connected to BZ which has been closed because of EOL --------------------+------------------------------ Reporter: jfilak | Owner: crash-catcher@… Type: defect | Status: new Priority: major | Milestone: Component: faf | Version: Keywords: | Blocked By: Blocking: | --------------------+------------------------------ https://bugzilla.redhat.com/show_bug.cgi?id=849833#c12
#919: don't reply with KNOWN response for reports connected to BZ which has been closed because of EOL ---------------------+----------------------------- Reporter: jfilak | Owner: crash-catcher@… Type: defect | Status: new Priority: major | Milestone: Component: faf | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------+-----------------------------
Comment (by jmoskovc):
I don't agree with this. The server shouldn't have any knowledge about the product EOL. I think the reporting process shouldn't just end and bz plugin should check the url returned from the server and create a new ticket if the given one is EOLed.
#919: don't reply with KNOWN response for reports connected to BZ which has been closed because of EOL ---------------------+----------------------------- Reporter: jfilak | Owner: crash-catcher@… Type: defect | Status: new Priority: major | Milestone: Component: faf | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------+-----------------------------
Comment (by jfilak):
Replying to [comment:1 jmoskovc]:
The server already has knowledge about the product EOL. The server uses this knowledge to filter out releases on the summary page (this causes that you don't see bugs for Fedora 15 etc.) From my point of view, the server should have comprehensive knowledge about a problem and should use this knowledge to give client instructions|advice how handle the problem on client's side. (e.g. it is not necessary to demand RedHat BZ ticket if there is a ticket in other tracking system and has everything required to fix the problem)
crash-catcher@lists.fedorahosted.org
-
fedora-badges