Component description for "Firefox for Android :: Build Config & IDE Support" is out of date
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
People
(Reporter: botond, Assigned: dkl)
Details
Attachments
(1 file)
The current component description is:
Fennec-specific build issues, and generation of Eclipse and other projects.
I assume this description was written at a time when Fennec was our only Android product, whereas today, the component is meant to apply to all Android products, including Fennec and GeckoView. So, I would suggest revising it to:
Android-specific build issues, and generation of Eclipse and other projects.
or
Build issues specific for Firefox for Android, and generation of Eclipse and other projects.
|
||
Comment 1•6 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #0)
The current component description is:
Fennec-specific build issues, and generation of Eclipse and other projects.
I assume this description was written at a time when Fennec was our only Android product, whereas today, the component is meant to apply to all Android products, including Fennec and GeckoView. So, I would suggest revising it to:
Android-specific build issues, and generation of Eclipse and other projects.
This one seems write. We should remove the mentions of Eclipse, since I removed that stuff in Bug 1196367.
or
Build issues specific for Firefox for Android, and generation of Eclipse and other projects.
I think the term "Firefox for Android" will not be the term of art for m-c for long.
I think we might want a component in "Firefox Build System" rather than under the product specifically, 'cuz the plan is for the build team to pick up most of this type of work moving forward.
+1 should I make that component in Firefox Build System and we can move the existing bugs to it?
|
||
Comment 3•6 years ago
|
||
Agreeing with emma's statement in comment 2, please move the component + existing bugs.
:dkl, is there a way we can make Build System the new parent, or do we need to make a new component and move the bugs?
|
Assignee | |
Comment 5•6 years ago
|
||
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #4)
:dkl, is there a way we can make Build System the new parent, or do we need to make a new component and move the bugs?
If it is just moving the component from one product to another (i.e. no component name change, etc.) it is simple. Same as when we move stuff to the graveyard product except just another product.
Cool, could you do that move if that's something that needs command line access? Then I can update the name and description post move.
|
|
Assignee | |
Comment 7•6 years ago
|
||
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #6)
Cool, could you do that move if that's something that needs command line access? Then I can update the name and description post move.
Yeah I would do the move first via cmdline and then you can edit the details after. So I just need to know the
SrcProduct DstProduct CompName
dkl
SrcProduct: Firefox for Android
DstProduct: Firefox Build System
CompName: Build Config & IDE Support
|
|
Assignee | |
Comment 9•6 years ago
|
||
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #8)
SrcProduct: Firefox for Android
DstProduct: Firefox Build System
CompName: Build Config & IDE Support
Ok not as simple as I thought. The versions and milestones between the two products are completely different. So a custom script will be necessary to map the values as they are being moved.
|
|
Assignee | |
Updated•6 years ago
|
|
|
||
Comment 10•6 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #9)
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #8)
SrcProduct: Firefox for Android
DstProduct: Firefox Build System
CompName: Build Config & IDE SupportOk not as simple as I thought. The versions and milestones between the two products are completely different. So a custom script will be necessary to map the values as they are being moved.
There's not a huge amount of value in the existing versions and milestones. Hopefully the custom script is not significant, but if it is, I think that losing that information is a viable option.
I think we will want to change the component name, perhaps:
CompName: Android Studio and Gradle Integration
|
|
Assignee | |
Comment 11•6 years ago
|
||
(In reply to Nick Alexander :nalexander [he/him] from comment #10)
There's not a huge amount of value in the existing versions and milestones. Hopefully the custom script is not significant, but if it is, I think that losing that information is a viable option.
I think we will want to change the component name, perhaps:
CompName: Android Studio and Gradle Integration
Unfortunately each bug must have some version associated with it. When we move a bug from one product to another, if the bugs current version does not exist in the new product, it can cause unpredictable results when trying to load it later. So we will need to assign it to some other legal value. Unfortunately the two products have different version/milestone values for the same version of Firefox for example. One has Firefox 67 and one has 67 Branch, etc.
|
|
Assignee | |
Comment 12•6 years ago
|
||
|
|
Assignee | |
Comment 13•6 years ago
|
||
Script has been ran to move the component.
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #6)
Cool, could you do that move if that's something that needs command line access? Then I can update the name and description post move.
Feel free to update the info and close this.
|
||
Comment 14•6 years ago
|
||
Done!
If there's a particular new bug template you want for this component, let us know.
We just enabled component-level bug templates.
|
|
||
Comment 15•6 years ago
|
||
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #14)
Done!
If there's a particular new bug template you want for this component, let us know.
We just enabled component-level bug templates.
I have never considered such a template. If anything springs to mind, I'll reach out. Thanks, Emma; thanks, David!
Description
•