[mistwang]

Thank you for your feedback.

We understand your points. We do not follow that route because it will really slow us down with bug fixes. We want to be stay agile/swift/efficient with bug fixes, and push bug fixes as soon as possible. We do have internal testing and beta user testing, but in real world production environment there are so many different scenarios so bugs will always come up after people use it in their busy production environment.

We update the current release package as soon as we confirm one bug is really fixed, we try the new build on client's production environment to make sure. Leaving current release package unpatched with a private secret bug fix release package potentially causes more trouble for our customers, also may result in duplicate bug reports, which causes more overheads for our development team to deal with.

A bug affect one customer may not affect others, as some bug fixes are for very special scenarios. You do not have to upgrade to the latest build as long as you are not experiencing any problem. If the bug is serious and generic enough that may affect many people, we will release a new bug fix version.

We will release a new version once current release is relatively stable and we do not receive much bug reports on it.

For a major new release, we often have a few bug fixes every day, we cannot increase the release version multiple times in a day. Even we do that, you still need to check the release/changelog page a few times a day.

Just ask yourself, for company strictly follows what you suggested, how soon you will see a bug fix? days? weeks? months? You pay for the fast turn around of bug fixes, not wait for next new release with tons of bug fixes.

There are a few options available for you:
1. avoid using a major new release, usually the first few minor releases of a major release will have more bug fixes, wait till 4.2.xx released, most bug should have been ironed out by that time.
2. try the cutting edge release, if any problem, send us bug report, back to the stable release (4.1.13 now), wait for next release.
3. do automated daily update from command line if you want to stay cutting edge,

/usr/local/lsws/admin/misc/lsup.sh -f -v <VERSION_NUM>

we will add an option to let user download the latest build of the same release to make sure all bug fixes applied automatically.