Closed
Bug 1497586
Opened 6 years ago
Closed 6 years ago
Release mozlog 3.9
Categories
(Testing :: Mozbase, enhancement)
Tracking
(firefox64 fixed)
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: jgraham, Assigned: jgraham)
Details
Attachments
(1 file)
There are a couple of changes I'd like to get out there.
Assignee | ||
Comment 1•6 years ago
|
||
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/autoland/rev/1f60cfed3bb3 Update mozlog version number for release, r=ahal
Comment 3•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1f60cfed3bb3
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Comment 4•6 years ago
|
||
Hi! The mozlog 3.9 release only includes a Python 2 wheel (rather than a universal wheel) and no sdist. This breaks the Treeherder python3-smoketest (which is helping us maintain the Python 3 readiness progress we've made so far): https://travis-ci.org/mozilla/treeherder/jobs/440059722#L687 Please could the python 3 wheel and sdist be uploaded? I believe this can be done via: `python3 setup.py bdist_wheel sdist` (now that there exists a non-universal wheel, it probably makes sense to upload a python3 only wheel, rather than a universal one for the 3.9 release specifically) To prevent non-universal wheels for future releases, this should be added to `setup.cfg`: ``` [bdist_wheel] universal=1 ``` It would probably also be worth having a docs "steps for releasing a new moz* package" section, or alternatively a script to do this, since the same thing has happened in the past too (bug 1477219 comment 5) - which isn't surprising given that releasing a new version is something that only happens once in a while, so hard to remember the exact steps :-)
Assignee: nobody → james
Flags: needinfo?(james)
Assignee | ||
Comment 5•6 years ago
|
||
Done. This really really really needs to be scripted.
Flags: needinfo?(james)
You need to log in
before you can comment on or make changes to this bug.
Description
•