(In reply to Alesandro Ortiz from comment #39) > Does Mozilla have an automatic disclosure timeline for this type of bug? I'd like to set a date of March 21st, 2022 for public disclosure of this bug and bug 1744158. > > Please let me know if the disclosure timeline is acceptable for both bugs. > > This allows over 14 weeks for both bug fixes to reach users. Just to be clear, I think you're counting from now, right? Release dates for 96 and 91.5esr are Jan 11, and Jan 11 - March 21st is just under 10 weeks, if I'm not mistaken? (not a comment on whether that's enough or otherwise, just trying to make sure we're all on the same page!) > Per comment #17, Chromium has embargoed their bug report until the date I request, which will be the same date that Mozilla agrees to here. I'm afraid I don't know the answer to this, but Dan or Tom should be able to help.
Bug 1705211 Comment 40 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Alesandro Ortiz from comment #39) > Does Mozilla have an automatic disclosure timeline for this type of bug? I'd like to set a date of March 21st, 2022 for public disclosure of this bug and bug 1744158. > > Please let me know if the disclosure timeline is acceptable for both bugs. > > This allows over 14 weeks for both bug fixes to reach users. Just to be clear, I think you're counting from now, right? Release dates for 96 and 91.5esr are Jan 11, and Jan 11 - March 21st is just under 10 weeks, if I'm not mistaken? (not a comment on whether that's enough or otherwise, just trying to make sure we're all on the same page!) I'm afraid I don't know the answer to this, but Dan or Tom should be able to help.