3.7 release

[max-cx]

Just last-minute collaboration to make the 3.7 release of Distributed Tracing and Telemetry happen on time.

[eromanova97]

Hello! We can discuss the rest on Monday, if you feel better. Please just do not feel like you have to answer, your health is a priority here! ❤️

[max-cx]

Thank you, Eliska.
I'll do my best to organize the info that you will need.
🙂Have a good weekend

[eromanova97]

Hello, to give more info here, in case you will be checking this thread, from the "epic" PR (that contains other release PRs:
Noting my observations regarding this PR:

• I could not find a similar PR for previous releases, so I suspect this is new process that was not present in previous releases
• This PR contains most of the content from the smaller linked PRs:
  • Intention seemed to be to have this merged, instead of separated PRs, to make the publishing easier
  • However, there is big piece of content in this PR (mostly in this commit: 10e983bb22a843e8c82ded4143420a897615911a) that is not present in smaller PRs, nor reviewed. This seems to be about restructuring of the docs
  • -> Because of this, I will be merging the other small PRs listed here instead, and then rebase the big one to not have the changes there lost (because I am not sure if the work is finished on that, plus there would have to be some additonal reviews for this), therefore I will follow the process from previous releases
  • As a result, you can finish the work on restructuring whenever you are back

In summary: the release content will be merged and the structural changes will be preserved in the big PR.

[max-cx]

@eromanova97, 🙂 here are my suggestions, which you can of course ignore if you choose:

1. The commit that you identified that contains restructuring changes is just content reorganization (i.e., no QE review needed). Since no one has done a peer review on it, I suggest that you do the peer review on that commit yourself (since I am the author). I would be asking for a peer review from a writer on the Observability team, which includes you, I just haven't made a Slack post with such a request yet.

2. If you do the previous point, then I suggest merging this one big PR (as per my emails from yesterday evening and this morning) and leaving the constituent small PRs open so that I can close them after my sick leave. If you don't feel comfortable merging the big PR yourself, perhaps ask Gabriel for a merge review?

3. The docs merge is indeed scheduled for today so that when the docs go live by tomorrow, the Operators will start getting shipped tomorrow. This novel reversed order is by design, following recent feedback from Support.

[eromanova97]

Hello! Oh, so a quick question, even when the release is planned for tomorrow, you want me to merge everything today?

[eromanova97]

@max-cx if you have time to check this, let me know, otherwise I will just merge first thing in the morning, it should not be that problematic, so no worries if you cannot react 🙂 please just rest 🙏

Regarding you point 1, I will peer review your changes and I can merge them as well 🙂 (I was not sure if the changes you made were all finished, that is why I initially was hesitant to merge them)

But those are just details, everything is finished and ready, so you don't have to worry about the release 🙂

[max-cx]

@eromanova97, 🙂 yes, please merge today.
According to Support, and with consensus from Engineering and Product Manager, going forward we merge and publish the docs just before the code release. So the plan for 3.7 is to ship the 3.7 code as soon as the 3.7 docs go live. So merging the docs this afternoon is planned timing because the docs will get published by sometime tomorrow, just in time for shipping the code. According to Support, it's better to have new docs without new code than to have new code without new docs.

[eromanova97]

Note to Max: I have all the issues mentioned in this PR's comment + release notes all reviewed and ready for release 🙂
I will merge the separate issues listed there, when the release is out, and will rebase this main PR afterwards.

So all the changes will be merged, and the changes in that big PR will not be lost.

[eromanova97]

Note: the eng let me know that the release will be tomorrow