1.5.0.9/2.0.0.1 blocker nomination deadline - Friday, November 10

[Jay Patel]

As we move on with our next security release, just wanted let people
know of a few key dates:

1. Blocker nomination deadline: Friday, November 10
2. Code Freeze: Sunday, November 26

Please nominate any bugs before 11/10 that you feel meet the strict
criteria for this release: topcrashers, security vulnerabilities,
critical regressions.

We are on a tight schedule, so owners of any blockers please submit your
patches for approval so we can get them landed asap! Thanks.
- Jay

[Axel Hecht]

For this minor update, I'll be handling the l10n queue again. As we have
discussed in the meeting yesterday, this affects l10n, too, as detailed
below. Cross-posting to .l10n.

Jay Patel wrote:
> As we move on with our next security release, just wanted let people
> know of a few key dates:
>
> 1. Blocker nomination deadline: Friday, November 10

For changes in localizations, I'll be handling this a bit flexible, but
please, get your requests out as soon as possible.

I think that the l10n approval queue is empty right now, so if you think
that I missed a request, make sure to poke me again.

> 2. Code Freeze: Sunday, November 26

This one is strict, for l10n, too.

> Please nominate any bugs before 11/10 that you feel meet the strict
> criteria for this release: topcrashers, security vulnerabilities,
> critical regressions.
>
> We are on a tight schedule, so owners of any blockers please submit your
> patches for approval so we can get them landed asap! Thanks.
> - Jay

Don't forget to use the fixed1.8.1.1 and verified1.8.1.1 keywords to
track landing and testing of your patches.

Axel