Please get us a better changelog

Discussion Hub General Discussion
1

Can you please include a changelog for every new version that mentions every change, no matter how small and no matter if a lot of people were talking about it in the forum, a single person submitted it to the zendesk or just the devs that changed it on their own.

I was testing some older bug reports I posted on the Zendesk and forum, and just now noticed they were fixed. You would probably stop a lot of complaining and help us with creating better bug reports if you include every little change. (as we can then better relate to what could have caused said bug)

I don’t think I have ever seen a sim where changelogs don’t include very specific information.
(Sorry for putting that bold, but if a dev sees this thread he has to see that :wink: )

Don’t:
improved flight model on some aircraft

Do:
improved flight model for A320 at low speeds
improved flight model for TBM 930 with crosswind
…

I know the list may end up being long, but it’s the same for other sims.
Perhaps keep the short version for the download screen, but give us a longer version somewhere.

edit: I just read the latest changelog and it seems like it contains some more info. Good. :slight_smile: I haven’t read it since the changelogs before that didn’t include much useful info. still, I’m sure the changelog does not include every change or fix as it should.

7 Likes
2

First off, I tend to agree with you about the change log.

But about that specific comment, people don’t tend to complain about things that are working, or log tickets for things that aren’t broken.

If they fixed it, it won’t generate new tickets whether they include it in a change log or not. It was either fixed, or it wasn’t.

3

It’s not about people complaining about things that are working, it’s about letting people know an issue they encountered is fixed.

4

Hmm before you submit to zendesk you should anyway confirm that the bug still exists in the current version.

Writing down every change would throw up more questions here in the forum than it does any good.

5

I reported the bug a day or three after launch. I tested it now and it was fixed. I did not have the intention to report it again, but I find it kinda stupid that I have to figure it out this way.

What if they consider something fixed, but I do not and I sit here waiting for months for it to be fixed? If it was listed I would have known I should opened up discussion again. (if worth it of course)

I disagree that detailed changelogs are bad. Here is an example of a changelog with a lot of depth:


Scroll down a bit as the start is about new vehicles. Note how much more depth the changelog contains. I feel like many hardcore simmers would appreciate that.

Another example of slightly more depth in the changelog:

Note that both changelogs include items that are not discussed by members, but just changed by devs.

Not to mention that many of us simmers are actually devs/scenery designers. We know very well how to read changelogs, and it’s certainly beneficial to us to know what’s happened behind the scenes.

6

Well if it is something that you need (is important for you), you will notice that it is fixed by trying it out. Otherwise it’s not important to know.

Do you really just “wait” until you touch the reported function/plane/scenery/etc. (whatever it is) again?

I stick to my opinion that too much info would do more harm than good.

Maybe they could do the normal (normal published as they do now) and a deeper technical changelog somewhere in a subforum for the technical people.

7

It’s in the initial post :wink:

8

I would love to get better change logs. make the request in the wishlist so we can cast votes.

9

I did, but the mods moved it. :smiley:

1 Like