I love the Slack changelogs 😂

Ubuntu new release changelogs be like:

- New number
- New funky animal

Latest facebook for iOS update is 219 mega-fucking-bytes. Yet, no real changelog to tell me what da fuck changed!!!!!! Fuck that developer for real!!!

Just in case you were wondering...

Gotta love witty changelogs

Changelogs are like a magazine for programmers...

I'll point names today

Boss: Quick! The Xero integration is not working anymore!
Xero Documentation: place your client secret in the HEADERS
Me: * places client secret in headers *
Xero API: Bad Request!
Me:
*re-reads documentation*
*creates new client secret*
*1 hour of trying*
Hmmmm
* places client secret in request body, not in headers *
Xero API: Ok!

UPDATE YOUR DOCUMENTATION
TELL US ABOUT IT IN THE CHANGELOGS

Can we talk about changelogs for a second?

Almost every major app in the play store has changelogs like "Improving your experience" or "We did some changes to enhance your experience".
Wtf is this bullshit. Is it that hard to write the actual changes in the changelogs so that I know what got changed, huh?
Guess its kinda hard to write " We are shoving more telemetry crap down your throat" in a changelog.

Fuck sake.

Multi-billion dollar company - don't write fucking changelogs

At least write "Fixed some fucking bugs" or something...
Is it that hard?

I hate when a software update changelog looks like this:

The latest update is now available, update your software to get the most out of it.

I want a fucking changelog before updating my things. Like: fixed a bug, new button with cool new feature. Just something. I have to know. Can't just install something blindly that could ruin my software, especially when it's not reversible..

updated my app and wrote "nobody reads this :/" into the changelog. did not thought that i was wrong :D

When the change log says "fixed bugs and improved performance" only to find the entire application has been redesigned.

!isNotRant(this);

I'm an avid user of Snapchat and have used it for quite a while, but there's always been something that pisses me off.

When an app gets an update, I'm quick to check the changelog and see what's now and what's been fixed. That's my little snippet of information I like to know on a release. And then there's Snapchat.

They put fuck all in their changelogs. By fuck all I don't mean a little bit of information, I mean they don't list anything. They, instead, lost features from their last major release which could've been 10 or so releases back. Even Twitter's "Fixed some bugs" is more informative than their bs.

So I ended up writing a well worded and surprisingly clean message in their feedback section about this, but I'm not expecting much. In short I said "You changelogs are crap, you need to put more into them to show a bit more respect, showing stuff from a few releases ago isn't helpful" and my favourite "if you can't do it in the team that releases, get the primary devs to write the changelogs for you".

I'm saying this here to see if anyone agrees with my opinion. If you're going to release an update, you really need to tell us what's updated.

Thoughts?

Reason I am an Android Developer:

10% - I want to make apps to serve humanity
90% - Meh, just wanna write some cool Changelogs

Is anyone else get irritated while upgrading apps and seeing changelogs as:
1. minor improvements
2. performance boost
3. information not provided by the dev
4. repeating changelogs from the past few updates.

just tell me what minor improvement u fixed?
where performance is boost?
how can I trust if tomorrow you decide to add some malicious code.

I don't know but it really irritates me. Sometimes I don't even upgrade the app until they have something in the changelog.

Maybe because I am getting old now.

I started my actual gig as CTO of construction group (Innovation Hub) a year ago. And it was a hell of a ride, implementing kind of a scrum-ban for project management, XP, peer-reviews, a git-flow, git commit message formats, linters, unit testing, integration tests, etc...
And it's the fun part because with the CIO we had to drive the board to do A LOT of changes in their IT/Innovation drive.

But in one year there is a lot of KPI that went up :
* Deployment: When I arrived it took three stressful days to deploy a new version of one application, once a month. Today we do it every week, and it takes three annoying hours.
* We had no test. NOTHING! Today we have 85% code coverage for the unit test, and automatic integration tests run by our CI server every day.
* We had almost no documentation. Today our code is our documentation (it automatically extracted and versioned).
* We had 0 add value in the use of git. With commit messages as "dev", "asked task", inside jokes and a lot of "fix" and "changes". Today we have a useful git, and we even use it to create our deploy changelogs (and it's only mildly annoying!).
* More important, the team is happy! They get their purpose, see betterment in their tech mastery. They started doing conception, applicative architecture, presentations, having fun.

There is still a LOT of bad things we are still working on, and trying to solve (support workflow and betterment). But seeing what they already did, I'm so proud of my TEAM! I'm a fucking asshole, workaholic, "just do it" kind of guy. But they managed to achieve so much. Fucking PROUD!!

A big, fat FUCK YOU to everyone who pushes out app-updates with generic "Improvements for speed and reliability" changelogs. I hope you and all your descendants, relatives, friends and pets get huge, hairy, painful warts between your buttcheeks that grow larger every day and return after every attempt to have them removed. Fuck you, and fuck your bullshit updates.

And if there are any devs on devRant guilty of this behaviour, fuck you too. I hope your sexual organs rot and fall off, and that you lose all your upvotes.

Changelogs can be fun 😄

Okay, we fucking get it guys, you wish that you'd get changelogs with every app update and they'd tell you everything and blah blah blah.
Fuck off
We're the only people who even check, it's not worth the effort. Unless a major feature was added or a well known bug was fixed, the "fixed bugs" is more than enough for the general public.

Ecma International, the organization in charge of managing the ECMAScript standard, has published the most recent version of the JavaScript language. ECMAScript 2016 (ES7 or JavaScript 7th Edition in the old naming scheme) comes with very few new features. The most important is that JavaScript developers will finally get a "raise to the power" operator, which was mysteriously left out of the standard for 20 years. The operator is **... It will also become much easier to search for data in a JavaScript array with Array.prototype.includes(), but support for async functions (initially announced for ES2016), has been deferred until next year's release. "From now on, expect smaller changelogs from the ECMAScript team," reports Softpedia, "since this was the plan set out last year. Fewer breaking changes means more time to migrate code, instead of having to rewrite entire applications, as developers did when the mammoth ES6 release came out last year."

How did you spend your weekend?

- 1 day wasted on trying to configure a project

- 1 day spent on formatting documentation ( including changelogs & mailing archives, project started in 1987? The repo still has files that were last updated 26 years ago )

Wow. 3 super descriptive changelogs in a row.

Why is it so hard to deliver decent changelogs with updates? (Looking at you, Google...)

Current side project: A Gradle plugin to automate the build.gradle for Minecraft mods through ForgeGradle, Minecraft Forge, CurseGradle, Maven, and soon, Git changelogs.

Needless to say, its coming along swimmingly!

Am I the only one who feels the change logs should be more specific?