Closed Bug 1494980 (bmo-release-20180925.2) Opened 7 years ago Closed 7 years ago

push updated bugzilla.mozilla.org live: mozillabteam/release-20180925.2

Categories

(bugzilla.mozilla.org :: Infrastructure, enhancement)

Production
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
bmo-push accept staging

People

(Reporter: dylan, Assigned: ckolos)

References

()

Details

+++ This bug was initially created as a clone of Bug #1493986 +++ This is the same as the previous push except the timeouts related to how mojo handles HTTP requests have been increased. bug 1487422 : Remove Phabricator section from MyDashboard and related WebService API bug 1490687 : Stop setting r+s on Phabricator attachments bug 1490708 : Ensure we always call DBIx::Connector->dbh before any DBI method bug 1491973 : Add GeckoView to BMO::Data special casing bug 1345673 : Open Bugzilla History in a New Window or Tab bug 1490901 : ReviewBoard stub attachments no longer make a redirect, download a text file instead bug 1455495 : Replace apache with Mojolicious bug 1492850 : Remove places where headers are printed bug 1468489 : Documentation points to https://landfill.bugzilla.org that is no longer maintained and will be shut down bug 1492511 : Code to updating subscriber values for current private bugs is throwing errors in the phabbugz log bug 1470536 : Add new GeckoView product to easy product selector on Browse and Enter Bug pages bug 1492346 : scripts/syncflags.pl should also add the target product to any tracking flags that the source product is a member of bug 1492926 : Handle DBIx::Connectors more appropriately bug 1473417 : Show often/recently used products/components on New Bug page bug 1490595 : Bugzilla update check should use https bug 1491850 : restoreSavedBugComment takes a really long time (100ms) bug 1493295 : Add short URL to each bug { "build" : "https://circleci.com/gh/mozilla-bteam/bmo/13275", "commit" : "af4b5c6453d4566397dba61529fc32c96d611ced", "source" : "https://github.com/mozilla-bteam/bmo", "version" : "20180925.1" }
yes, the version number specified in the version.json is the same as the previous release. This is annoying but not an actual issue.
This is "live" but didn't get formally deployed (monkey-patched).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
No longer blocks: 1399721
You need to log in before you can comment on or make changes to this bug.