Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
Last night, I got the following question in email and it seemed like a good one and worth sharing the answer more broadly.
I'm just a bit curious about why you have an NDA for your SLCTP's. The purpose of NDA's is to prevent people talking about all the new great stuff in upcoming releases. I would imagine at this stage the products are feature complete; only performance and bugfixing left. You yourself have gone publicly out and said that performance kind of sucks in the Beta releases. So it's not something anybody else will trumpet on their blogs and use as an example of how crap Microsoft products are. The only thing I can see is that people will say that performance is great; and I would have though that was a message you would want to put out as much as possible.
No, it has nothing to do with that.
Let me start by saying I am not a lawyer. I’m passing on the legal advice we’ve been given and I haven’t drilled into it to really understand the reasons behind it. When we are given legal advice that I think really compromises our business decisions, I do sometimes drill into it and will put pressure on the legal team to find better solutions. In this case, I didn’t feel this was an onerous issue, and we had bigger fish to fry – like actually working on the perf issues being reported, so I let it go.
Our goal is to turn out the SLCTPs quickly and with very little overhead. We generally start delivering them to customers within a few days of the build completing. In order to do this, we have to bypass a lot of our release verification – some security verification steps, legal compliance steps, etc. We still do some – like code signing and virus scanning but a bunch is skipped. The legal team has told us that to distribute builds that have not gone through the full release process like these, the must go to a limited number of people and they must be under NDA. By distributing SLCTP1 to >50 people, I think we’re pushing the limits of “a limited number of people” but not too bad.
In general, I don’t care if you talk about the perf or not. In fact, if you have constructive feedback, even if painful to read, I want to see it. But, unfortunately, you can’t talk about it relative to the SLCTP builds for the reason I gave. We’re working on a plan for a more broadly available, non-NDA build. I’ll let you know when we know more.
Thanks,
Brian
Just out of curiosity... what does "SLCTP" stand for?
This post was linked from the home page of MSDN, so you'll probably get quite a few visitors who aren't familiar with this acronym (myself included).
Super-Limited Community Technology Preview
It was kind of a joke when we first called it that but it stuck :) We've had CTPs (Community Technology Previews) for a long time and they have been broadly available for anyone to download and try.
Between Beta 1 and Beta 2, we did a couple of CTPs that we only distributed to MVPs, early adoptors and close partners. We called them LCTPs (Limited Community Technology Previews).
After Beta 2, we decided we neede to provide some builds to people who had experienced performance and/or functional issues with Beta 2 so that we could confirm that we had properly diagnosed and fixed the problem. These builds were only going to be distributed to specific people who reported issues and agreed to verify the fixes. We coined the term Super-Limited Community Technology Preview (SLCTP).
Now I can barely pronounce the acronym any more :) I think there's a reason most acroynms are only 3 letters :)
Of course soon they'll be referred to as slick tips (two syllables only!) and we'll all forget about their origin :0)
Tom