Someone recently realized (bug 1415870) that it had been more than 2 years since we last updated Firefox's internal copy of the PSL. This is unfortunate because we maintain the actual list on publicsuffix.org . We should ensure, via whatever means is most appropriate, that we keep the list up to date. There are scripts for this purpose so it should take someone approximately 5 minutes at a time, but we need to make sure we have a process, and maybe a test or some other QE or automated check when we merge to beta (ie ideally not a week before release!) that we've updated it "recently" for some meaning of the word. We've had bug 1083971 on file to make updates automatically via Kinto, which (if fixed) would mitigate this somewhat, though we should still ensure that the list is up-to-date when shipped, too. Either way, the current state is not OK. Jason, given that the list lives in networking, can you (find someone to) own coming up with people/process to ensure we keep the list updated?
Gerv, you used to update our copy of the .dat file yourself. What do you suggest is the best process now?
Flags: needinfo?(jduell.mcbugs) → needinfo?(gerv)
:jduell: The PSL is now maintained in a separate repo to Firefox. I feel this means that we, the PSL team, maintain the PSL, and it's up to PSL consumers to take whatever copies of it they want at whatever time they want. So if Firefox wants to have a regularly-updated PSL, you either need a process for making sure it gets regularly updated, or move the data to Kinto, or whatever you want to do. A process could be manual or automated - whatever you prefer. The only thing I am sure of is, in the nicest possible way, it's not my problem :-) (What I do accept responsibility for is my failure to make this clear in the past two years; the current situation is my fault, and I apologise for that.) Gerv
Back to Jason given comment #3. :-)
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1459891
You need to log in before you can comment on or make changes to this bug.