By way of reminder, if you are including new bits in this edition of the simultaneous release, you'll need a release record that indicates the version that you are contribution. There's more help in the wiki
If you have not engaged in a release review
in the last year, then you will need to engage in that process ASAP.
Note that, per the IP Policy updates approved by the Eclipse Board of Directors in October 2019, piggyback CQs are no longer required. I owe you all a much longer discussion about these changes (which are more extensive than just not needing piggybacks) which I promise to provide before the end of the year. I've started here
Note also that, even if you are contributing new bits, but do not require a release review because you've done one in the last year already, the intellectual property contained (and referenced by) your release must be fully vetted by the IP due diligence process.
The simultaneous release participation rules require that projects consume third party content via Eclipse Orbit, so this shouldn't be a problem for most of you. For those projects that consume third party content from outside of Orbit (e.g., those projects that consume NPM content), or are otherwise unsure of due diligence status of any of their content, you can submit an IP Log and I'll take a look.
Director of Open Source Projects | Eclipse Foundation, Inc.