It won't be 9920. Why? Too old Also... Gabe said they will announce the 21 when the JTP will be released, this mean "in fact it's awesomely broken for now so please let us see how to fix bugs and then we will tell you when we release it".
It's not a matter of when. The point is 9920 builds have been compiled for almost 48 hours and 9920 seems to be frozen. Newest 9920 builds can still be compiled in the very short term (thus still be labelled 9920). Keep in mind that, historically, official releases (previews as well as RTM) go public several weeks after they're compiled and frozen (Gold, etc.). It's still the very same here so it's highly unlikely the JTP build's compilation date remains within a week range of its official release. It's just an observation on my part though...
Yep, at least, that's what we were sold by MS... "Awesome" did they say... well, we'll see very soon... or ?
Thank you for translating, I'm just think he is hungarian too, and I can't write pm because I don't have enough post in this forum. I apologize to everyone!
... but Build 10.0.9920.0.fbl_marketplace_dev01.150112-2313 was compiled afterwards... Although we couldn't care less about builds with a fbl_marketplace_dev string bit, it shows that more 9920 builds are (still) being compiled, whilst 9921 compilation has started as well... Weird you say? Anyway, only/still 7 days to go... will patience be rewarded this time?
Just keep checking buildfeed and when a build comes up in the main flight level that will be the build we'll get!
h t t p://ms-vnext.net/Win10esds/ is a much better source to know what .esd are done and dusted. I'd enjoy having to play with one of those: 9921.0.150112-1700.fbl_awesome1501_CLIENTENTERPRISE_VOL_x64fre_en-us.esd or 9920.0.150110-2153.fbl_awesome1501_CLIENTENTERPRISE_VOL_x64fre_en-us.esd ... wouldn't you? We're getting hotter and hotter, that's for sure. Roll on next week!!
So what? I don't understand your point... It's (supposedly) build 9920 and not 9921. The fact the string's (supposedly) labelled as fbl_marketplace doesn't show/prove anything. Unless proven, a (and this) screenshot is only what it is... a picture (fake or real).
if real it shows some changes that are not in 9901 (even though its a fbl_marketplace) so you could care a little for fbl_marketplace_dev string btw the screenshot is quite similar to the concepts leaked by cnbeta.
Well... for the record, there are currently 57 lab strings on Windows 10's development schedule so fbl_marketplace_dev is irrelevant among them (just one among tens of others). It stands to reason that what you'd find in one lab branch is also part of others, whatever their name. Differences may be small and depend on developer work groups only, who implement and tests bits on their own. Of course, if you compare builds 9920/9921 to 9901 (even thanks to what we know so far) you're 100% sure to find big visual differences indeed. It seems obvious enough without a screenshot as we're one week away from the JTP. Again, you compare builds 9901 and 9920 (based on a screenshot) whereas I'm talking about fbl_awesome and fbl_marketplace_dev lab strings... (a bit like comparing apples to oranges I may say...) so, yes, one couldn't care less about this or that lab string.