this post was submitted on 01 Oct 2024
635 points (98.5% liked)
tumblr
3480 readers
1 users here now
Welcome to /c/tumblr, a place for all your tumblr screenshots and news.
Our Rules:
-
Keep it civil. We're all people here. Be respectful to one another.
-
No sexism, racism, homophobia, transphobia or any other flavor of bigotry. I should not need to explain this one.
-
Must be tumblr related. This one is kind of a given.
-
Try not to repost anything posted within the past month. Beyond that, go for it. Not everyone is on every site all the time.
-
No unnecessary negativity. Just because you don't like a thing doesn't mean that you need to spend the entire comment section complaining about said thing. Just downvote and move on.
Sister Communities:
-
/c/TenForward@lemmy.world - Star Trek chat, memes and shitposts
-
/c/Memes@lemmy.world - General memes
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If they're not telling you in the patch notes it's probably because there is so much code churn that to retroactively document every fixed bug would amount to too much work.
That being said: if you have good git commit messages and pr bodies this process is very much automatic (at least ton GitHub) releases can have a bunch of notes from the merged prs automatically such as "PR #3964 Fixed thing at place when condition".
Also sometimes if I don't want to admit just how badly I screwed up, I put "#Fix 824 : fixed various issues" as opposed to "#Fix824 : fix to repair the fact I put the wrong select statement in the query in the last upgrade" because who wants to have THAT in the notes?