Microsoft decides to stop communicating the list of bugs still present in the new Builds that are released from Windows 10

When a developer company has in mind the launch of a product, one of the fundamental aspects is the correction of errors. These can be overlooked by development teams, so collaboration with the common user becomes essential

With this reason the betas arrived, powers even more with the expansion of network connections. The user can thus access a release before anyone else in order to help the developer to polish the bugs that are generated on a day-to-day basis.Some betas that we have seen in games and all kinds of applications. And the operating systems were not going to be less.

We have them for Apple (Apple Beta Program), Android (Android Beta Program) and Windows (Windows Insider Program) In this way, new functions can be tested before anyone else, but this entails a logical consideration that is not always it has to happen. And it is that we will be handling a _software_ under development that may contain errors and these are the ones that we must monitor and communicate through _feedback_ with the company on duty.

"

In the case of Microsoft, testing is carried out by launching the different Builds in the Rings that make up the program . We have seen how to access them and the degree of risk that one or the other entails."

Some builds that have always been released with a _changelog_, this is the list of new features that they include and that was accompanied at the end of a list of errors or failures that were still presentA good idea for beta testers to be very clear about the errors experienced.

This list, a true classic in the _builds_ released, however, it has become history with Build 16273 and in which we no longer find the list of bugs yet present An absence that has prompted some users to raise the issue on social media, a question that in this case was answered by Brandon LeBlanc, Insider Senior Program Manager.

According to LeBlanc, given the maturity of the Builds released at this point in the Fall Creators Update (we already know that Redstone 4 is on the rise), they don't consider it necessary to have to this list will continue to appear at the end of the changelog of each released Build.

This is a change that they say is irreversible and will not only be present in the already evolved Builds.In such a way that the list of present errors becomes history except in cases in which the severity of the failure or error makes it advisable for it to be notified

A difficult decision, it must be said, which surely many of the Insider Program participants did not like, who saw in this list a good way to carry out the checks in a much more efficient way efficient. What do you think of this decision taken by Microsoft?

Source | MSPoweruser In Xataka Windows | We tell you how to receive Windows 10 PC and Windows 10 Mobile Builds