Re: Proposal: Asynchronous blocker review process (using Pagure)

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

 



The RFE commit have been merged on master: https://pagure.io/pagure/c/31280551ec2fdf282152abae2ff9d44f20faaf92?branch=master

I'll notify here once we release 5.9 and upgrade pagure.io with it.

19/12/5 10:06(e)an, Kamil Paral igorleak idatzi zuen:
On Thu, Dec 5, 2019 at 9:33 AM Julen Landa Alustiza <jlanda@xxxxxxxxxxxxxxxxx <mailto:jlanda@xxxxxxxxxxxxxxxxx>> wrote:


    19/12/4 15:34(e)an, Kamil Paral igorleak idatzi zuen:
    On Tue, Dec 3, 2019 at 10:22 PM Tim Flink <tflink@xxxxxxxxxx
    <mailto:tflink@xxxxxxxxxx>> wrote:

        Has anyone poked at scoping out the work required for either
        the bot or
        the enhancements we would need for pagure?


    Lukáš Brabec looked into it, and creating a new Pagure ticket is a
    matter of a few lines of code (already written). Extending BBA
    with a "discussion link" in each blocker row should be trivial as
    well. I think that's all we need for trying it out.

    The blocker bot watching and updating the issue should be fairly
    easy as well, I hope, but as described above, we've hit an issue
    where Pagure API doesn't allow comment editing. Lukáš implemented
    a workaround that adds a new metadata field on the right side of
    each Pagure ticket showing the count summary. It's barebones, but
    at least something. We've haven't yet looked into writing the
    listener code, that would listen for Pagure events on the message
    bus and react to them. We also haven't looked at Bugzilla updater
    as described in the proposed workflow (that's really a cherry on
    top, we don't need it right away).
    Implementing an api endpoint to edit comment is easy, open an RFE on
    pagure's issue tracker if you need it and I'll take it


I'm not going to say no to that! :-) Here it is:
https://pagure.io/pagure/issue/4683
Thanks a lot.

_______________________________________________
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

_______________________________________________
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