Okay. We've cleared that up for the particular Build time 141217-1931. The lab string alone cannot predict the one meant to be released this month of January 2015.
21 January is Microsofts Consumer Event, fbl_awesome is the build they are showing and releasing... it's even confirmed, just like their ass backwards build strings is Year-Month-day, so 1501 is also year-month and whats on in the first month of 2015? Microsoft Consumers Event... >.>
Microsoft announced it's going to be Consumer Preview without any information on the lab string. That particular lab string 1501 has many Build versions listed under it which some are already leaked privately. I doubt if the 1501 is actually what you said it is. It is more of identification to me.
It's of no use resorting to discouraging idiomatic expression. I think you aren't really looking at what I am talking about. Well, January 21st release will prove if you are correct of your claim.
No, my claim is that it's releasing in the first month of 2015 which is January, not a specific date. Microsoft may not release the build on the 21st but it's highly likely they will as they launched windows builds often enough on event dates.
Don't count your chickens before they're hatched. We have seen that happened in our forecast of Windows 9 and the Build version only to be presented with version 10 at the end. Some of the Build versions of that particular lab string 1501 are already leaked privately during the December time of 2014. What do you think about that?
Only difference now is not only has fbl_awesome been officially announced, but KB3025380 changed the build lab used for flighting in the Insider builds to "fbl_awesome1501". What do I think of that? Nothing! Because that isn't relevant at all! Please explain, what do you think about that?
"Private leak" is a term used on Buildfeed.net, he probably doesn't have a clue what it means... A buildstring on Buildfeed can be a "Public Release", a "Public Leak", "Logging" or a "Private Leak". The first two don't need any explanation, "Logging" is when the internal update mechanism in the Insider builds is used to probe MS's servers for builds and buildstrings by changing the buildlab in the registry. Finally, "Private Leak" is everything else, a buildstring in leaked screenshots, a buildstring in a Microsoft presentation, a trusted source passing a buildstring to the Buildfeed staff, ... It doesn't necessarily mean the build is floating around the web (but it could be).
I haven't disputed part of the lab string 'fbl_awesome'. My argument is that we cannot tell it is going to be 1501 to mean January 2015 for the fact that some parts of that acclaimed January 1501 have been leaked privately. Thank you for referencing that patch code. Microsoft makes KB3025380 as an improvement for possible future updates(fbl_awesome) for Insider's participants and the update is for 9879(Public Build) and doesn't seem to apply to 9901(Private Build - which that particular lab string 1501 belong to). The relevancy of that question is Microsoft might distance itself from private leaks as official release come January 21 for Consumer Preview in a nutshell. That somebody claims 1501 is an identification standing for January 2015 is what my argument is mainly centered around. I think there is no argument to say Microsoft is going to release Private Build as Consumer Preview. However, I stand corrected.