From 46bcb831b9e32f825fef459b52bc12ceb3d7a7b3 Mon Sep 17 00:00:00 2001 From: Kohei Yoshino Date: Sat, 2 Dec 2017 10:43:46 -0500 Subject: Bug 1417980 - Fix non-HTTPS links and outdated links where possible --- Bugzilla/Extension.pm | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'Bugzilla/Extension.pm') diff --git a/Bugzilla/Extension.pm b/Bugzilla/Extension.pm index 7e53d87f3..baf2286e1 100644 --- a/Bugzilla/Extension.pm +++ b/Bugzilla/Extension.pm @@ -325,7 +325,7 @@ L. If you need a new hook for your extension and you want that hook to be added to Bugzilla itself, see our development process at -L. +L. In order for a new hook to be accepted into Bugzilla, it has to work, it must have documentation in L, and it must have example @@ -618,7 +618,7 @@ return C<0> or some false value. If you've made an extension and you want to publish it, the first thing you'll want to do is package up your extension's code and then put a link to it in the appropriate section of -L. +L. =head2 Distributing on CPAN @@ -628,7 +628,7 @@ distribute your Bugzilla Extension through CPAN. The details of making a standard CPAN module are too much to go into here, but a lot of it is covered in L -and on L among other places. +and on L among other places. When you distribute your extension via CPAN, your F should simply install itself as F, @@ -659,7 +659,7 @@ uses extensions. If you are an extension author and you'd like some assistance from other extension authors or the Bugzilla development team, you can use the -normal support channels described at L. +normal support channels described at L. =head1 ADDITIONAL CONSTANTS -- cgit v1.2.3-24-g4f1b