Skip to content

(@fluent/gecko) Prune obsolete build targets #471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2020

Conversation

stasm
Copy link
Contributor

@stasm stasm commented Apr 9, 2020

Currently, only the following targets are still used in Gecko:

  • FluentSyntax.jsm is used in tests,
  • fluent-react.js is used in Devtools.

I wondered about Fluent.jsm -- it's still used on the release channel in Firefox 75 today. If there's a any problem with it in the nex few weeks, I'll bring the Fluent.jsm target back.

@stasm stasm requested review from zbraniecki and Pike April 9, 2020 12:49
Copy link
Contributor

@Pike Pike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, Localization.jsm still claims that we're building it from here. It's also exempt from linting in m-c based on that ;-).

We should probably file a Core::Intl bug to clean that up?

I don't have huge concerns over this, but I'll leave the actual review to Zibi. Left a couple of nits on the makefile changes, I didn't test that.

@stasm
Copy link
Contributor Author

stasm commented Apr 15, 2020

@zbraniecki Would you mind taking a quick look at this? It's just some removals that I'd like you to be aware of. Thanks.

@zbraniecki
Copy link
Collaborator

lgtm!

@stasm stasm merged commit 55d26c1 into projectfluent:master Apr 16, 2020
@stasm stasm deleted the prune-gecko branch April 16, 2020 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants