Jason Sutherland - What's the hardest part of managing Longhorn's build process?

Sign in to queue

The Discussion

  • User profile image

    Longhorn has been promoted as a 'bet the company' product and release. I had wondered some time ago how the release team is coping with the pressure.
    It is great to see that the guys in charge of the Longhorn release can still smile and enjoy working on one the most talked product drops in Microsoft's history Smiley.

    Hopefully we'll hear more from Jason soon.

    - Chris

  • User profile image
    A bit off topic but the interviewer was difficult to understand.  It would be good to get him on mic as well.
  • User profile image
    That takes me back - when I started at Microsoft eight years ago, I worked in the Windows build lab.  This was back when we were working on SUR, and IIS 1.0.  We used SLM instead of SD, and there were no VBLs.  Working in the neck of the software development funnel was quite an experience back then - and I'm sure the challenges of the job have not decreased over the past eight years.

    10 points to anyone who can identify all the acronyms I used above.  (Ok, only 5 points if you are an MS employee.)
  • User profile image

    Shell Update Release = SUR
    Internet Information Services  IIS
    Service Level Management = SLM
    Solution Developer = SD
    Visual Build Labs = VBL

  • User profile image
    You got two out of five right - keep trying!
  • User profile image
    SLM is an internal source control solution. I believe the acronym officially expands to "Source Library Manager", but everyone I knew referred to it as "slime" (I had some interaction with it when I was interning at MS in 2000).

    SD is Source Depot, another internal source control tool that superceeded SLM. I believe SD shares some lineage with the publicly available Perforce product.

Add Your 2 Cents