Closed Bug 1121247 Opened 9 years ago Closed 9 years ago

Actually switch bzexport to the new bzapi compatibility layer endpoint

Categories

(Developer Services :: Mercurial: bzexport, defect)

Product:
Developer Services
Component:
Mercurial: bzexport
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gps, Unassigned)

References

Details

Attachments

(1 file, 1 obsolete file)

bzexport: switch to new bzapi endpoint ()
5.01 KB, patch
sfink
: review+
Details | Diff | Splinter Review 
Somehow we actually forgot to switch bzexport to the new bzapi endpoint in bug 1033394. Derp.
bzAPI is now part of BMO. We no longer need a dedicated config option to
declare its URL. Instead, we compute the URL from the Bugzilla URL.

We add a warning indicating that the old config option is now
deprecated and should be removed.

While we were here, some legacy documentation has also been cleaned up.
Attachment #8548518 - Flags: review?(sphink)
bzAPI is now part of BMO. We no longer need a dedicated config option to
declare its URL. Instead, we compute the URL from the Bugzilla URL.

We add a warning indicating that the old config option is now
deprecated and should be removed.

While we were here, some legacy documentation has also been cleaned up.
Attachment #8548520 - Flags: review?(sphink)
Attachment #8548518 - Attachment is obsolete: true
Attachment #8548518 - Flags: review?(sphink)
Attachment #8548520 - Flags: review?(sphink) → review+
No more legacy bzAPI endpoint usage \o/
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: