Add a section on "Expedited Releases" to the Release Policy

[niallkp]

The following discussions on members@ talked about urgent releases where the voting period was less than the normal 72 hours:

• https://lists.apache.org/thread/v6ypw13s1r3zc6xmvbl10mzfgbcjw4xf
• https://lists.apache.org/thread/ks9r0t3x8w5k5fy707dhphgnt2k7j7nd

It is difficult to have a consensus on what an exceptional circumstance is. No-one has disagreed with urgent releases for publicly know security issues. However there was agreement from a number of people (and no disagreement) on the following points:

• Explain why in the vote email
• give project members as much "heads up" as possible before the vote is called
• since its not following normal policy it must be reported to the board

I've tried to encapsulate that in a new section in the release policy doc. However I'm not the best wordsmith so please feel free to improve

[markt-asf]

Looks good to me. Just the one trivial nit with the proposed text.

[tisonkun]

I'm considering mentioning this at the beginning of this page, since we use the keywords throughout the whole page. Or we can leave the whole reference to RFC-2119 to a follow-up since the explained content here already implies that such a "72 hours" SHOULD can be broken in exceptional circumstances.

[niallkp]

Its a good point and there are other policy docs also using SHOULD, I wondered the same, but just focusing on this issue and the debates it seemed a good idea to have it close to this wording. Lets see if anyone else agrees with you before deciding whether to remove it from this change

[tisonkun]

Yeah .. It would be OK to improve the reference in a follow-up also.

[justinmclean]

At the top of the page would be better I think