Skip Menu |

This queue is for tickets about the BZ-Client CPAN distribution.

Report information
The Basics
Id: 121584
Status: resolved
Priority: 0/
Queue: BZ-Client

People
Owner: Nobody in particular
Requestors: raphael.crochet [...] actia.fr
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: [EVOLUTION] BZ::Client, XMLRPC API vs REST API
Date: Tue, 9 May 2017 10:25:54 +0000
To: "bug-BZ-Client [...] rt.cpan.org" <bug-BZ-Client [...] rt.cpan.org>
From: Raphael Crochet <raphael.crochet [...] actia.fr>
XMLRPC API will be deprecated in the future of Bugzilla. I didn't find your roadmap, do you plan to support the REST API of Bugzilla ? It would be cool that BZ::Client could support either XMLRPC API or REST API. This would be a good thing for sustainability of code using BZ::Client. Raphaël CROCHET Technology Department Fixe : +33 (0)5 82 08 05 42 [logo_ACTIA_mail_2017] ACTIA Automotive (siège social) 5, rue Jorge Semprun B.P. 74215 - 31432 TOULOUSE cedex 4 (FRANCE) http://www.actia.com<http://www.actia.com/> [icon_mail_youtube]<http://www.youtube.com/ActiaOfficialCom> [icon_mail_linkedin] <http://www.linkedin.com/company/actia> [icon_mail_web] <http://www.actia.com/> ............................................. Ce courrier électronique ainsi que tout fichier qui y est joint est destiné exclusivement aux personnes ou institutions dont le nom figure ci-dessus et peut contenir des informations protégées par le secret professionnel, dont la divulgation est strictement prohibée. Tout message électronique est susceptible d'altération. Actia décline toute responsabilité au titre de ce message. Le contenu de ce message ne représente en aucun cas un engagement de la part de notre société. Si vous n'êtes pas destinataire, nous vous avisons que sa lecture, sa reproduction ou sa distribution sont strictement interdites. Nous vous prions en conséquence de nous aviser immédiatement par retour de ce courrier et de supprimer ce message et tout document joint de votre société. Merci. This email message and its enclosures is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. Any e-mail message is subject to alteration. Actia disclaims all liability in connection with this message. The content of this message does not represent any commitment from our company. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message with its enclosures. Thank you.
Download image001.jpg
image/jpeg 9.5k
image001.jpg
Download image002.jpg
image/jpeg 1.4k
image002.jpg
Download image003.jpg
image/jpeg 1.3k
image003.jpg
Download image004.jpg
image/jpeg 1.8k
image004.jpg
Hi Raphael In the pod of BZ/Client.pm I have spoken about the future of this module: --------------- BUGZILLA VERSIONS ^ Please note that this BZ::Client module is aimed at the XMLRPC API available in Bugzilla 5.0 and earlier. For 5.1 and later, which have a totally different REST API, please see Net::Bugzilla. As such, I welcome all patches (via pull request) for functionality relating to 5.0 and earlier. I will only actively hunt down bugs relating to the 'maintained' Bugzilla server softwares. Please upgrade your server and duplicate the problem, or see the above commitment to accept patches to fix for older versions. --------------- The design of the BZ::Client I am not very happy with, for example this is very strange: my $client = BZ::Client->new( %etc ); my $bugs = BZ::Client::Bug->get( $client, $ids ); It really should be more like: my $client = BZ::Client->new( %etc ); my $bugs = $client->bug( $client, $ids ); So when I took maintainer role of BZ::Client, I spent lots of time expanding all the functionality to match the 4.4 XML RPC API (sorry, i missed the file upload). But the plan is to use the change to REST api to provide a more comfortable API for programmers.
Subject: RE: [rt.cpan.org #121584] [EVOLUTION] BZ::Client, XMLRPC API vs REST API
Date: Wed, 10 May 2017 12:40:22 +0000
To: "bug-BZ-Client [...] rt.cpan.org" <bug-BZ-Client [...] rt.cpan.org>
From: Raphael Crochet <raphael.crochet [...] actia.fr>
Hi Dean, Thank you for your quick answer. I didn’t notice the ‘Bugzilla Versions’ advice. Unfortunately, I could not find the Net::Bugzilla module in CPAN. The only thing I saw is Net::Bugzilla::Kanbanize which seems not very alive since June 2014. I agree with you about API and about your plan. Have you a target date for the REST support? Show quoted text
________________________________ De : Dean Hamstead via RT <bug-BZ-Client@rt.cpan.org> Envoyé : mercredi 10 mai 2017 01:47:24 À : Raphael Crochet Objet : [rt.cpan.org #121584] [EVOLUTION] BZ::Client, XMLRPC API vs REST API <URL: https://rt.cpan.org/Ticket/Display.html?id=121584 > Hi Raphael In the pod of BZ/Client.pm I have spoken about the future of this module: --------------- BUGZILLA VERSIONS ^ Please note that this BZ::Client module is aimed at the XMLRPC API available in Bugzilla 5.0 and earlier. For 5.1 and later, which have a totally different REST API, please see Net::Bugzilla. As such, I welcome all patches (via pull request) for functionality relating to 5.0 and earlier. I will only actively hunt down bugs relating to the 'maintained' Bugzilla server softwares. Please upgrade your server and duplicate the problem, or see the above commitment to accept patches to fix for older versions. --------------- The design of the BZ::Client I am not very happy with, for example this is very strange: my $client = BZ::Client->new( %etc ); my $bugs = BZ::Client::Bug->get( $client, $ids ); It really should be more like: my $client = BZ::Client->new( %etc ); my $bugs = $client->bug( $client, $ids ); So when I took maintainer role of BZ::Client, I spent lots of time expanding all the functionality to match the 4.4 XML RPC API (sorry, i missed the file upload). But the plan is to use the change to REST api to provide a more comfortable API for programmers.
I had a sponsor to bring BZ::Client up to 4.4 and am happy to maintain it (adding you patches for example) - but I don't have a sponsor for REST API yet. So, unfortunately I can't provide an estimate.
closing ticket