Changelog

James

Retired Customer Support
Messages
1,315
Social Credit
1
It depends on the type(s) of thing(s) we are adding/changing to whichever client when we push an update. If we are adding a new feature or changing how a module works, it will always be in the changelog. Sometimes we will push smaller updates to patch bugs as we fix them so our users do not have to wait for the next feature / module release to have bugs fixed. When that is the case we will either log the updated feature(s) / fixed bugs internally, then whenever we release the next module / feature update we will include the things we've done in the smaller patches leading up to the update in the larger update's changelogs (even though they were technically done on an earlier version), or we will just not say anything in the changelog at all.

Some times we prefer to keep things we are changing / adding / doing with our clients private, and play our cards closer to our chest to prevent competition from copying us or people who are acting against Vape to counter it. Or, whatever we have changed in the client is so insignificant and irrelevant (for example, we recently updated something in Vape V3 to fix a unicode font bug for Chinese users, but we only kind of fixed it -- the bug is still there it's just less prevalent. That is super insignificant and irrelevant to 99.99% of our user base so we didn't waste time adding a Vape V3.27.0.1 Update Log) that we don't really find it important to update the changelog to reflect the fix/change/modification.

Hope that answers your question.
 

James

Retired Customer Support
Messages
1,315
Social Credit
1
Why dont you guys show the changelog for your older clients like vape v2, I'd like to look into that I remember you guys used to but not anymore how come?
Because when you'd open the changelog it'd make the page 10000 meters long. Maybe we'll put a static version of the old V2 changelog on another page if we can find some time (and find the changelog, lol).
 
Top