Re: Blockerbugs discussion tickets feedback 🐞💬

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 20, 2020 at 02:04:51PM +0100, Kamil Paral wrote:
...snip...
> I'd much rather see something like:
> 
> ====
> Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1875677
> 
> The bug seems to have been proposed as a blocker/freeze exception in
> [comment 13](https://bugzilla.redhat.com/show_bug.cgi?id=1875677#c13).
> ====
> 
> That makes it easier to find the blocker/FE proposal with the justification
> and everything (including sometimes the criterion). I'm just not sure it's
> worth the effort, because usually it's not that difficult to find it
> manually with Ctrl+F. And of course the implementation would get messy once
> there are multiple and not just one proposal, the bug is reopened from a
> previous release cycle, etc.

This could be nice indeed. Most of the time you are right and it's easy
to find the proposal in the bug... but on occasion there's a ton of
comments and it's not so easy. 

Anyhow, this was just a thought, if there's no way to implement it
currently then there isn't. The new process is still a win on lots of
other levels. :) 

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux