Hello Forum and Litespeed Tech. First of all, sorry for my English. I think it's time to speak about your system of release, because actually, it's not sustainable: We speak about a commercial product, then a lot of people pay for this software. Every software, usually, follow this method: think -> developing -> private testing -> beta public testing -> rc -> release. And this is the first problem. You don't follow this system: we don't know future plans, known bugs per version. We only have a little change log Now, assume that version x.y is available for the public (like 4.2.0, or 4.2.1): Every user download the new version, and test it on private server. If someone find a bug, it open a thread on this forum, and if it's approved, you update the same version. So, every day, I need to check if someone of the staff update the version (for example 4.2.1), and what is corrected in this new version. So, same numbers, and no change log. This is a "method" request: if you release version 4.2.1 to the public, and I send a bug report, please, don't update the version 4.2.1 but add a version, if you like numbers 188.8.131.52 and a change log. I repeat: we can't stay all the day on this forum to read if someone find a bug, or if you update the package. Thank you, and good work.