As a community that volunteers, it is unrealistic to expect certain events to meet scheduled timelines as shown on the following page:
According to the goals listed and laid out, phpBB 3.2.x has reached "EOL", meaning there should technically be no further updates or support for it. It isn't being followed anyways since phpBB 3.3.x hasn't been released yet. So to that I say, get rid of the page, and if the developers can and wish to continue to support the active phpBB version that is current, while the upcoming release is still in development, then they should be allowed to support it with updates. This way there is no date showing that the "End of Life" has been reached, because the page will not exist.
Back in 2007, phpBB 3.0 was released and had 8 years of support. Good! There is no reason why modern versions of phpBB can't receive the same treatment. And I think they should. Volunteers should not follow a "Release Process" page because this is not a corporation that focuses on profits. This is a community that volunteers because they want to without the restraints or limitations of deadlines. Or at least, that how it should be.
The concept of having this schedule does not align with the principles of what volunteering is about. Volunteering should be freely given with code changes to support a release for as long as the volunteers wish, until their next "gold" release is ready. They can anticipate when that will be without providing a release date to the public, and still give 6-months of EOL support notice to the current and mature version in the form of an Announcement.