Thanks for the clarification, I thought that the process of officially
freezing the spec included the public review period, that we freeze the
spec internally after our own review by HCs/ICs and the TG, and
officially freeze the spec after receiving comments from the public
review, while we review them (so that no more comments can come in). The
definition of the freezing state
(
https://wiki.riscv.org/display/HOME/Specification+States) used for
marking documents on github is not clear on this, it says "a change will
only occur because of some truly critical issue being identified during
the public review cycle" but it doesn't clarify if the public review
happens before or after marking something as officially frozen. Also the
page we use for tracking
(
https://wiki.riscv.org/display/TECH/ISA+Extensions+On+Deck+for+Freeze+Milestone)
is titled "extensions on deck for freeze milestone" and even extensions
like Smepmp that have "frozen & out for public review" checked are still
there (on deck for freeze milestone, as if they haven't reached the
freeze milestone / official freeze yet). Also the "Ratification Policy"
doc
(
https://docs.google.com/document/d/1-UlaSGqk59_myeuPMrV9gyuaIgnmFzGh5Gfy_tpViwM/edit)
includes the public review process under the "Freezing Milestone"
section, it even says "All public review comments must be resolved..."
and "Public review comments and responses will be stored in the top
sheet." (the top sheet for the freezing milestone) so one may think that
even resolving the public review comments is also part of reaching the
freezing milestone. The only document I found where it's clear that
public review happens after we reach the freezing milestone is the
"extension lifecycle and milestone definitions"
(
https://docs.google.com/presentation/d/1nQ5uFb39KA6gvUi5SReWfIQSiRN7hp6z7ZPfctE4mKk/edit#slide=id.ga0a994c3c8_0_6)
which is inconsistent with "Ratification Policy" since it includes the
public review and the resolution of public review comments as part of
the vote-ready milestone.
I updated the doc on github to be consistent with "extension lifecycle
and milestone definitions", marking the spec as frozen.
Regards,
Nick