Thank you, Quentin. I understand that things can get bogged down around releases. Unfortunately, my confidence in FRR isn’t too high at the moment because of this issue. Michael
On 16 Aug 2021, at 15:41, Quentin Young <qlyoung@nvidia.com> wrote:
Issues are tackled on a volunteer basis like everything else in the project. We haven't parsed through issues lately because our volunteers have been busy handling release logistics among other things. A week delay is not uncommon.
If you mean the "triage" label, that is added automatically to new issues; you would have had to remove it, similar to how you would have had to manually remove the issue report template that is prefilled in the comment box that we ask all issue reports to use.
The reported bug looks fairly straightforward, hopefully someone can pick it up soon.
Quentin
________________________________________ From: frog <frog-bounces@lists.frrouting.org> on behalf of Michael H Lambert <lambert@psc.edu> Sent: Monday, August 16, 2021 3:31 PM To: frog@lists.frrouting.org Subject: [FROG] Action on Issue in GitHub?
External email: Use caution opening links or attachments
I was just wondering if there is some special incantation needed to move issues opened on GitHub into a triage state. I submitted #9344 a week ago and it has not progressed.
Thanks,
Michael
----- Michael H Lambert, GigaPoP Manager Phone: +1 412 268-4960 Pittsburgh Supercomputing Center/3ROX FAX: +1 412 268-5832 300 S Craig St, Pittsburgh, PA 15213 USA lambert@psc.edu
_______________________________________________ frog mailing list frog@lists.frrouting.org https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.frrouting.org%2Flistinfo%2Ffrog&data=04%7C01%7Cqlyoung%40nvidia.com%7C9091601e8d0a491464c508d960ecb0ce%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637647392066747601%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=NgVlNd%2F7vfuQqqCIIh79%2Bx1aQPYrC4gvuVpfeGSGmn0%3D&reserved=0