Not saying any of the issues mentioned above are because of this, but it could show how software is often developed using a branch system.
So you get to a point in the new software, you leave a place holder and go on working, you leave another place holder, and so on and so on, then something goes wrong so you go back to an earlier place holder, but what one, the previous one before the fault or do you go back further because it turns out the seed for the fault is three builds back.
So a scenario like this is perfectly feasible:
Manus 31 wrote:
"For instance we have the quite hours flashing notification which was an issue in one of the earlier builds.Then it was fixed and now it is back again"
As said I am not saying this is what happened in this case, but it is the sort of thing you expect to see in software development.
And you all have to remember that is what is happening here, you are all playing about with software that is still a work in progress, it makes sense to flag up issues so that the developers can see what is happening, but to just moan and whinge is stupid as you all signed up for exactly this sort of stuff happening.