Okay. I think it depends on the angle you view it from. Something leaked privately is only available to few who have no prerogative to release it to the public due to the privacy policy guiding the use. I find this post interesting though. That people think what I feel private leak mean is appalling to say the least. I know what Private leak, private and public Builds mean. There is no way any of my posts suggest otherwise regarding the definition of their differences. You made that up and pretend that is what I think.
The leaked 9901 build is from is from winmain_prs and not fbl_awesome, i mean not even sure what's so hard to understand here, fbl_awesome1501 is a mere name, not a compilation date. Do you really believe 1501 means nothing when we already have confirmation that fbl_awesome is what Microsoft will release this month? What are you even trying to say? Microsoft is going to release a Private Build as Consumer Preview? I mean do you even read your nonsense? Meh...
Lots of confusion here over fbl_awesome1501. I think we are just getting a bit bored since previous leaked build, I assume. The patch has already been confirmed to change the flighting to fbl_awesome1501. So it's not very likely that they would change that again. We can really only guess on it's relevance. My assumption at the moment is that fbl_awesome1501 is private right now while it is in internal testing at Microsoft, which I believe is an even smaller group compared to some of the other build strings which is why we aren't seeing any leaks on this. They are trying to keep it wrapped up for now as best they can until the event in January. At that time, likely on the 21st at the event, fbl_awesome1501 will open the flood gates and will at that time become a public build once they change the permissions on how they control the build strings. So it will come through automatically for those who have patched their builds, or Win7, Win8.1, etc. As for what the numbers refer to in fbl_awesome1501, it's really anyone's guess. As for why buildfeed.net refers to some of the fbl_awesome1501 builds as Private Leak, we would have to ask Thomas Hounsell to know for sure. But my guess on this one is that buildfeed's servers maybe couldn't identify those builds, and so someone on the inside leaked the build information to them. I personally don't think that it means that a build was actually leaked because otherwise we would see screenshots and so on. Anyways, as I said most of this stuff we can really only guess on. So I figured I'd join in on that part of the discussion. Here's hoping for another leaked build soon to give us more to talk about!
its possible that fbl_awesome1501 builds are w.i.p. builds and when finalised or ready for release it will be released publicly as fbl_awesome simply, why make a big deal out of this anyway? will it change anything?
Thank you very much. I am not making a big deal out of it at all. There is nothing wrong in pointing out something questionable in a discussion. The fact that he often uses abusive terms to reply my posts makes me to prove what my argument is centered around.
A Private Build is not Private when it's Public, you understand this right?... Eitherway this is getting too stupid, have fun.
Wow! That looks like a rhetorical question though. We seem to get ourselves confused of what leads us to this stage. Let's agree to disagree. I accept the whole build source types are getting pointless. Thank you, bro. I am still going to run my Consumer Preview as main OS come the release day. I appreciate your understanding at last.
Because it's there for all to see, there is the evidence in other discussion threads as well. Any way let's get on to the topic, I guess it would be good if the build that is going to be released as Consumer Preview is leaked before it is announced or released officially as it not only gives the enthusiasts some thing to cheer about early in this New Year but it also gives Microsoft a wider testing platform, which can help them iron out most of the issue before releasing a Consumer Preview to a more wider audience.
I never made anything up, I never said what you think it is, I just said what it actually is and that I suspect you think otherwise. There are tons of posts that suggest you don't understand what "Private leak" means, for example... The source listed in buildfeed isn't in any way related to whether or not a build will be released as Preview or not!!
Didn't take long before the bitching started over one little thing... (the fbl-awesome branch thingy) Anyway I don't care about that let's just focus about the next released build coming this month
Seriously, you did! I know you are looking for an easy exit, sir. However, the Consumer Preview in that context is meant for the Public as per what really differentiate it from private build( a small group made of people who are meant not to diverge it to the public at that particular time or in time to come) regardless of the source types(private or logging) you are alluding to here.
That baffles me a lot! Really, I think they misunderstood me all along. I would have to quit from showing my enthusiasm for Windows OS here.