This is just an example, but there really needs to be a way to make sure they post a proper changelog... Like, is there a limitation on characters? Can't we set up a way to import the release notes from Github? Why is it this way?
this post was submitted on 05 Sep 2023
72 points (100.0% liked)
Free and Open Source Software
18019 readers
102 users here now
If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would say it is this way because it takes a big effort to crunch all the patches that have been made thus far and make an easy-to-read summary out of them.
It's not something that comes for free. You need someone on the job.
concise Commit Messages are the solutions. :)
Even if the commit message is concise, there is a difference between what the patch does on a technical level and what the end user will see as a result.
IMO the solution is to link each commit to an issue or a ticket - some high-level description of the feature the commit implements - but there still has to be someone who makes the effort of making sure each commit is linked to a ticket and who nags the devs when they forget to do so..
Understandable... but what about the bigger companies?
Those are profit driven. If they can cut cost they will. They just want the minimal effort to get customers. Also usually their app has such marketing and notoriety that most people don't really care about changelogs.