Closed Bug 772419 Opened 8 years ago Closed 8 years ago

turn off qt + rpm builds

Categories

(Release Engineering :: General, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: emorley)

References

Details

Attachments

(2 files, 2 obsolete files)

As far as I know these serve no purpose anymore. We should just shut them off. Not sure who I should cc to verify that assumption.
Blocks: 774813
Since we're no longer shipping Meego builds, I think these have outlived their usefulness.
Attached patch Remove qt support (obsolete) — Splinter Review
Assignee: nobody → bmo
Status: NEW → ASSIGNED
Attachment #643381 - Flags: review?(bhearsum)
Attached patch Remove rpm build support (obsolete) — Splinter Review
Attachment #643382 - Flags: review?(bhearsum)
Is it hard to keep Qt builds? they are serving for making Meego N9/Qt mobile builds easier, so Qt builds are not broken after every second commit.
Also Meego seems not very dead after Jola company took Meego support and promised shipping new devices based on Qt.
Meant to add in the comment when attaching, that the patches were pending on final confirmation as to what we want to do. Similar to comment 0, I'm not entirely sure who we need to CC on this for approval either way (even if we keep Qt, we may still want to get rid of the RPM builds etc).
(In reply to Oleg Romashin (:romaxa) from comment #4)
> Is it hard to keep Qt builds? they are serving for making Meego N9/Qt mobile
> builds easier, so Qt builds are not broken after every second commit.
> Also Meego seems not very dead after Jola company took Meego support and
> promised shipping new devices based on Qt.

Qt not a Tier 1 platform for us (https://developer.mozilla.org/en/Supported_build_configurations) and will not close the tree when there are issues with it. I assume that whomever it is that is doing the Meego N9/Qt mobile builds has some form of continuous integration, so can bugs not be filed based on its output?
bsmedberg started a thread on dev.planning to figure out what support level the QT builds should be at: https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/yMwsSHPPkCs
Unbitrotted
Attachment #643381 - Attachment is obsolete: true
Attachment #643381 - Flags: review?(bhearsum)
Attachment #646178 - Flags: review?(bhearsum)
Unbitrotted. Applies after the other patch.
Attachment #643382 - Attachment is obsolete: true
Attachment #643382 - Flags: review?(bhearsum)
Attachment #646179 - Flags: review?(bhearsum)
Comment on attachment 646178 [details] [diff] [review]
Remove qt support

There was nothing in the newsgroup thread indicating that these should be Tier 1 builds. I'm sorry to the folks that do find these useful, but we're going to go ahead and shut them off.
Attachment #646178 - Flags: review?(bhearsum) → review+
Attachment #646179 - Flags: review?(bhearsum) → review+
Attachment #646179 - Flags: checked-in+
Comment on attachment 646178 [details] [diff] [review]
Remove qt support

Landed both of these on the default branch. The next reconfig will merge them to production and stop the builds.
Attachment #646178 - Flags: checked-in+
In production.
All done here.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.