Project committers can put whatever dates they want into the release and release review date fields. My expectation is that project teams will adjust these dates as their schedule adjusts and the real date for their release becomes more evident (ideally as early in the release cycle as possible). Very often, however, the EMO actually ends up adjusting the dates on behalf of the project team as release review requirements are completed (i.e., IP Log reviews, PMC approval, and specification committee ballot). Note that this means that, when adjusting this information is left to the EMO, it occurs very late in the process.
FWIW, when the EMO detects that a release review is imminent (e.g. a project initiates a PMC approval, submits their IP Log for review, or calls a specification committee ballot), the EMO creates a tracking issue in Bugzilla with the project leads (and whoever initiated the action) in copy. That issue is then used to track the release process. We use consistent naming on these tracking issues (e.g.,
ee4j.jaxrs) to make them easier to find.
In this particular case, I should have adjusted this last week when the specification committee ballot was initiated. My apologies.
Thanks for drawing this to our attention. I've adjusted both the release and release review dates to November 4.