Conversation
static/releases/upcoming.md
Outdated
| @@ -1,2 +1 @@ | |||
| We continuously improve and extend the model. | |||
| No significant updates are confirmed for the next version, but stay tuned for future releases. | |||
| The model is continuously being improved and extended. No specific updates are confirmed for the next release, but stay tuned for future releases. | |||
There was a problem hiding this comment.
Don't you want to say something about direct emissions here?
There was a problem hiding this comment.
I'm quite sure that the direct emissions stuff will not yet be ready the next deploy. Therefore I did not include it.
There was a problem hiding this comment.
Isn't it okay to be a bit more flexible in what we put under upcoming changes? We can even state that it is not yet definitely in scope, but potentially.
There was a problem hiding this comment.
Should we then leave out the date in upcoming too? Because now it explicitly says 30 April, but if we want to generally be more flexible in describing what's upcoming (and it not being certain yet whether it's the coming deploy or thereafter, or thereafter), then maybe it makes more sense to not put a date there...
2 participants
Context
This PR adds the release notes and inputs and gqueries changelog for deploy 2026-03.