Status... status and more status. This is something new I'm trying, and I'd love to hear your feedback on the process. As most people at Microsoft (heck probably anywhere), I have to send weekly status internally to my peers, the big cahunas and other interested parties. My status covers MSBuild, and pretty much reports a pulse for the entire feature area. What's Dev up to... what's QA up to... is the PM *still* slacking off (<-- don't answer that). So if internal folks are generally interested in it... perhaps *you* are interested in it as well.
So the question for you is: Well are ya interested in it?
I will attempt to post these on a regular basis, and through it, you can know what's up in MSBuild land. Again we'll tweak the frequency and granularity of these as we go. The more feedback you give... the better I'll be able to optimize this experience for you... Onto status then:
Beta 1 Progress
So that concludes the status... you are now UP TO DATE <-- in msbuild speak that means you will be skipped next time we build you :) (ok dorky joke but I couldn't resist)
Useful? More of it? Less of it? Inquiring minds want to know :)
1 Nightlies - we have ~2100 distinct automated tests for MSBuild. Some more important than others. Nightlies are some of the most fundamental tests we run. As their name implies we run these on a daily (ahem nightly) basis and they are meant to test critical customer scenarios. Breaking or regressing a nightly is really bad. Nightlies are a great indicator of our overall product stability. 2 OGFs - Overall Good Feeling or Overall Goodness Factor (I can never remember). A few times per milestone our awesome QA organization tests end-to-end scenarios (both manually as well as automated). Based on the end-to-end experience they issue an OGF for the scenario. The collection of these OGFs isused as an indicator of our overall product quality. Example of an OGF for MSBuild would be “Logger Initialization and Shutdown“3 Handshakes - A collection of cohesive OGFs bubbles up into a Handshake. If all OGFs within a handshake pass then a passing handshake is issued. If at least one OGF does not meet expectations the entire Handshake fails. An example of an MSBuild handshake would be “MSBuild Logging Handshake“ which would contain all MSBuild OGFs.4 Flavored Project - these are project that build ontop of our core VB/C#/J# project systems and tend to optimize for a given technology. Examples of these “flavored“ projects are the Smart Devices, VSTO or Yukon projects. 5 Note - This is build.exe as we run it internally within our build labs. Number may vary if you hand author your makefiles from scratch.
_*_*_*_ Update: Swapped the 4th and 5th footnotes. Thanks goes to David Cumps for pointing that out. _*_*_*_