Enhanced release documentation #103
-
|
I like it very much, how fast you (@raffaelschneider ) are working and how good you are … But one thing is very important: I hope, this is OK for you … |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Thanks for the feedback @Lord-KalEl, totally fair point, and I appreciate you raising it. We're still in the early phase right now, so things move fast and releases come frequently as we iron out bugs and fill gaps. The plan is to slow things down once we hit 1.0.0 and feel confident in stable, uneventful, predictable operability. At that point, the idea is to move to an LTS + Nightly release cycle, though that's still taking shape. In the meantime, every release has a CHANGELOG entry explaining what changed and why: CHANGELOG.md. I'll make sure that stays up to date so you always have a clear record. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, the problem is only half solved: |
Beta Was this translation helpful? Give feedback.
-
|
Hey @FreeSynergyNet You're right, the release workflow was generating notes with installation and verification instructions but wasn't pulling in the actual changelog content. That's been fixed in Starting with the next release, the GitHub Release page will include a "What's Changed" section with the full changelog entry (the same content from CHANGELOG.md). If there's no changelog entry for a given tag, it'll link to the CHANGELOG directly as a fallback. Thanks again for flagging this, appreciate the follow-up. |
Beta Was this translation helpful? Give feedback.
Thanks for the feedback @Lord-KalEl, totally fair point, and I appreciate you raising it.
We're still in the early phase right now, so things move fast and releases come frequently as we iron out bugs and fill gaps. The plan is to slow things down once we hit 1.0.0 and feel confident in stable, uneventful, predictable operability. At that point, the idea is to move to an LTS + Nightly release cycle, though that's still taking shape.
In the meantime, every release has a CHANGELOG entry explaining what changed and why: CHANGELOG.md. I'll make sure that stays up to date so you always have a clear record.