Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile Insider
-
For many insiders (including me) early access to inbox app updates is a fundamental part of being in the Fast Ring and there were many "protests" when this access was blocked, as I have said several times, this was the main reason to implement Skip Ahead .
My point still stands though. RS3 must be the priority now
-
-
For many insiders (including me) early access to inbox app updates is a fundamental part of being in the Fast Ring and there were many "protests" when this access was blocked, as I have said several times, this was the main reason to implement Skip Ahead .
Favor, please. Just me, or maybe not enough coffee yet, but what exactly does that mean? tks
-
For many insiders (including me) early access to inbox app updates is a fundamental part of being in the Fast Ring and there were many "protests" when this access was blocked, as I have said several times, this was the main reason to implement Skip Ahead .
Agree, the most enthusiastic insiders want to have the latest under construction apps available for testing at all times. Personally I hate when suddenly after an update I have some very ancient App with a lot of missing functions, when I could use a perfectly functioning beta App that makes my life much easier.
One good example would be OneDrive Client. I hate the default one, but the latest beta is awesome. :)
Example: I upgraded from 16251.0 to 16257.1 and my OneDrive client got downgraded. But later I got it update to an even newer version than I had before.
-
I can't see why MS thought skip ahead was a good idea for it's testing program. Surely MS's priorities must be in getting the RS3 release solid.
I assume they need to start work on the more major changes in time to hit the next release? Also the work to get RS3 solid is perhaps now in a phase where it's more focussed on testing than development, so may not require so much resource from the development teams, leaving them free to spend some time on the next version.
-
-
I assume they need to start work on the more major changes in time to hit the next release? Also the work to get RS3 solid is perhaps now in a phase where it's more focussed on testing than development, so may not require so much resource from the development teams, leaving them free to spend some time on the next version.
Oh that is where you are wrong, NOW is the time they need to triple or quadruple resources for bug fixing or they won't get the release done in time. It is easy to design and add a new feature, but it takes a lot of time and effort to fix bugs.
-
Oh that is where you are wrong, NOW is the time they need to triple or quadruple resources for bug fixing or they won't get the release done in time. It is easy to design and add a new feature, but it takes a lot of time and effort to fix bugs.
Yes it does.
-
Especially if over half of the bug fixing staff have no clue how the code or other windows internals currently work. 
-
Agree, the most enthusiastic insiders want to have the latest under construction apps available for testing at all times. Personally I hate when suddenly after an update I have some very ancient App with a lot of missing functions, when I could use a perfectly functioning beta App that makes my life much easier.
One good example would be OneDrive Client. I hate the default one, but the latest beta is awesome. :)
Example: I upgraded from 16251.0 to 16257.1 and my OneDrive client got downgraded. But later I got it update to an even newer version than I had before.
Favor, please. Just me, or maybe not enough coffee yet, but what exactly does that mean? tks
In this thread many users explain that: Introducing Skip Ahead for Windows 10 Insiders in the Fast Ring
I think this is the best explanation: Introducing Skip Ahead for Windows 10 Insiders in the Fast Ring
-
Oh that is where you are wrong, NOW is the time they need to triple or quadruple resources for bug fixing or they won't get the release done in time. It is easy to design and add a new feature, but it takes a lot of time and effort to find and fix bugs.
fixed that for you.
My point being that when something is near to release, a lot of the effort will probably move into Testing, not Development. That's certainly my experience (admittedly I've never been involved in writing an operating system). It can take a lot of effort to find the bugs but once a bug is found it often doesn't take long for developers to fix.
So at this point in the cycle I'd expect the testers to be busy finding bugs, but the developers have some time to start work on the next release.
-
-
Especially if over half of the bug fixing staff have no clue how the code or other windows internals currently work.
There must be a lot of badly written legacy code in Windows that is quite difficult to modify without unintended effects.
Quote