3.1.8 vs 4.0.1

[KGC]

So now that 3.1.8 is out after 4.0.1, does it mean that the issues 3.1.8 addresses from the 3.1.7 release are still present in the 4.0.1 release? Or are these completely separate branches with their very own "issues"?

[rapoint_person]

I'd say this is a valid question when comparing any two functional releases with each other. I'd like to see some schematics over the different functional/major releases and be able to see a "bug sync" between releases. Quite important actually!

[reaper]

Bugs are always checked vs the versions "under construction" and if applicable fixed in both versions, where possible/applicable both branches are kept in sync (new or changed features in 4.0.1 that don't need fixing have not been fixed ofcourse and issues in 4.0 that are not present in 3.1 are not ported backwards)

bugfix info is included in release notes

[migration]

Yeah,
that's true. I posted sometimes ago a post about the unuseful Release Notes because they report always the same informations, excpet to the new and addressed issues.
It would be most important (our customer ask us everyday) have a release notes similar to the other vendors ones, when you (and your client) can see immediately what's changed, what's is now different then in the previouvs version and wht I have to upgrade.

Thanks