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.

Highlights

• Whidbey and Yukon SxS Nightlies passing 100%
• QA signed off on all Beta1 Tripwires
• We did a Final Pick Up of Yukon bits

Today my inbox was flooded with opinions about the VS Data team status post that was inspired by the MSBuild status post. These come to me because a large portion of my job currently revolves around figuring out and encouraging how Devdiv participates in the community. I spent too much time addressing concerns today not to share my responses publicly.

What keen observers are witnessing is a division in the midst of a transition towards a more transparent and customer connected future. Transitions can be painful and a lot of people fear change like guy who refuses pants in the old Quiznos adds. This transition has been one with a lot of experiments. Some stick, some don’t, and some are refined into something different but better. The old adage says crawl, walk, and then run. We are heading into the walking phase of our “community” efforts.