[META] Migrate usage of brandProductName from DTD and properties to Fluent
Categories
(Firefox :: General, task, P3)
Tracking
()
People
(Reporter: nordzilla, Assigned: kpatenio)
References
Details
(Keywords: meta)
As part of the M2 milestone for arewefluentyet, we need to remove the DTD and properties usages of brandProductName from our startup path, migrating them to use Fluent.
|
||
Comment 1•3 years ago
|
||
I feel like this is more a META/tracking bug than an actual bug?
Strings using brand namees are scattered all over the place, I don't think it makes sense to migrate one string out of 10 for a feature/window/panel, just for the sake of getting rid of the branding files.
Take this recent example: we have 3 new strings, added as part of a bug that landed around 10. Only 2 use brandShortName, which would leave all the rest behind, and code in a weird mixed state.
(In reply to Francesco Lodolo [:flod] from comment #1)
I feel like this is more a META/tracking bug than an actual bug?
Strings using brand namees are scattered all over the place, I don't think it makes sense to migrate one string out of 10 for a feature/window/panel, just for the sake of getting rid of the branding files.
Take this recent example: we have 3 new strings, added as part of a bug that landed around 10. Only 2 use brandShortName, which would leave all the rest behind, and code in a weird mixed state.
I agree, I think it would be appropriate to label this as a META bug. brandProductName is used in various .properties and brand.dtd files.
Could we start a new bug removing brandProductName from brand.dtd files that blocks this?
@nordzilla, any thoughts on filing this as a meta bug?
|
Reporter | |
Comment 4•3 years ago
|
||
Yes, I agree. I will change this into a meta bug.
|
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 5•3 years ago
|
||
:kpatenio - is that ready to be closed now that all dependencies are resolved or should we scope out more?
(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #5)
:kpatenio - is that ready to be closed now that all dependencies are resolved or should we scope out more?
I believe this should be ready to be closed.
(wasn't sure if someone was going to close the ticket)
Description
•