Create 3.4.1 release notes #444
Conversation
alexanderahn
commented
Nov 21, 2024
•
alexanderahn
commented
- To see the specific tasks where the Asana app for GitHub is being used, see below:
- https://app.asana.com/0/0/1208563654736896
There was a problem hiding this comment.
the image shadows look different from sept, oct, and nov. can we standardize?
docs/release_notes/2024/nov2024.md
Outdated
|
|
||
| It enables proactive alerting when resource utilization approaches defined thresholds, ensuring timely intervention before limits are reached. Additionally, it supports the suspension of critical services in the event of resource overflows. | ||
|
|
||
| For more information, see Alerts Configuration. |
There was a problem hiding this comment.
should there be a link here? where do i find "alerts configuration" ?
There was a problem hiding this comment.
Yes, I'm waiting on the alerts config doc to be merged first. This probably makes a good reason to use release branching in the future.
There was a problem hiding this comment.
Makes sense. yes, release branches would help with this!
docs/release_notes/2024/nov2024.md
Outdated
|
|
||
| #### Extended Maintenance release | ||
|
|
||
| Release 3.4.1 is our first Extended Maintenance (EM) release. These releases provide you with a long-term support Prophecy version. |
There was a problem hiding this comment.
Will all future releases be EM releases? Or is it only some releases? Or, is it all releases on an opt-in basis?
Or maybe I do not understand at all 🫠
There was a problem hiding this comment.
Okay I found the answer in your other PR! So in this case, i might clarify along the lines of:
Release 3.4.1 is our first Extended Maintenance (EM) release, offering you the option to choose a Prophecy version with long-term support.
docs/release_notes/2024/nov2024.md
Outdated
|
|
||
| - **Execution Metrics bug fix**: We fixed a bug where Execution Metrics is disabled but turns on during interactive execution. | ||
|
|
||
| - **Blank config package field bug fix**: We fixed a bug where the Python Pipeline would crash after clearing the config package name and then attempting to save. |
There was a problem hiding this comment.
| - **Blank config package field bug fix**: We fixed a bug where the Python Pipeline would crash after clearing the config package name and then attempting to save. | |
| - **Blank config package field bug fix**: We fixed a bug where a Python Pipeline would crash after clearing the config package name and then attempting to save. |
agree?
|
To update libs version on release day. |
Update Scala libs version
