Clarify that new concerns will cancel FCP

[HarHarLinks]

idk this is a wild guess about what seems reasonable

Pull Request Checklist

• Pull request includes a changelog file
• Pull request includes a sign off
• Pull request is classified as 'other changes'

Signed-off-by: HarHarLinks [email protected]

Preview: https://pr2057--matrix-spec-previews.netlify.app

[HarHarLinks]

Alternatively, it would seem reasonable that after resolving the concern, FCP can be proposed again.
Seeing as the SCT already agreed on FCP, restarting FCP automatically would be the lighter approach.

[richvdh]

I don't think this is correct. IIRC, a concern stops the FCP completing, but doesn't stop the 5-day timer. In other words, if the 5-day timer elapses while the concern is active, the FCP will complete as soon as the concern is resolved.

[tulir]

The next bullet point already says concerns block the FCP completing, but don't reset the timer, so I don't think any changes are needed?

[turt2live]

as others have said, this isn't what is done in practice. Concerns are intended to prevent the FCP from starting or finishing depending on where it's at, but it doesn't cancel the FCP (cancelling means we have to re-acquire all checkboxes).