Below is a fragment form my exchange with the release management office

gregory.dorman 09:55
OK, I apologize again, for sill learning the process, I am not trying to be annoying. Below is my understanding of next steps - can you tell me which of the below are not correct?
We all believe what we have in bb-10.5-release/build-33670/ is a "final candidate"
Assuming no out-of-the-blue emergencies, this is what will be posted for community (I don't know how the "posting" actually works, but that would be next lesson, not now).
We do intend to submit this package to one last regression run before posting
Theoretically (and ideally), this is also the 10.5.4-2 Enterprise. It shall be tagged by all submodules in accordance with their tagging rules, but all of that converges on 10.5.4-2.
Henceforth the only thing that can cause another build of community is a failure of the "final regression run" and subsequent correction.
And the only thing that can cause another build of the Enterprise is a correction to something truly catastrophic, should it come out of the field.
How am I doing?

serg 11:01
Yes. Almost. ColumnStore doesn't build on sid and doesn't install on SUSE. We may skip it on these platforms or I may fix it if there's time. Not a blocker. Spider doesn't install, will check later today. Marko wants another bugfix in, I'm not sure I agree with that.
Yes. Almost.
Yes, this is automatic in builbot
Enterprise is that plus its own enterprise stuff. We don't have a rule for tagging submodules, so it's up to you.
11:04
All main things are in, we are not waiting for anything as such. But as it's a weekend, I can look at small embarrassing-but-not-showstopper issues this evening.

gregory.dorman 11:17
Re re regressions. I suppose regression that BB launches automatically is for the server, maybe for some other engines, but somehow I feel it does not launch any regression for Columnstore. Which leads me to believe we will need to do it "by hand" (have our QA produce executables, run the suites). Is this correct?
Re Enterprise rules. Stand corrected - yes, plus its own enterprise stuff. At present columnstore does not have anything in that category. The intent to keep the two the same. Except - if something crucially bad is found in final candidate of enterprise after the community is posted.
Should that happen, I suppose we would apply "EE tag" after the fix, creating temporary divergence
--> provided the correction is not the first instance of "enterprise only" (in which case a new repo will have to be created, and the whole lot more that this entails). There is no realistic or even speculative expectation that this might happen this time around.
It also seems that the build of "final candidate" for the enterprise is still pending. Given that it needs to be regressed as well, I am expecting that we would have to do it "by hand" also, once it is there.
If above is correct - is there an expected time for the EE final candidate build?

serg 11:19
Correct, by hand. Until you'll have a decent regression suite in mysql-test