Whidbey leak late last week

As many of you know, late last week we sent mail out to Whidbey alpha participants alerting to them to the announcement this week.  I was particularly excited to send that mail because we had some real news in the mail about the Express skus – not tons of detail and not lots of advance…

2

Whidbey: opaque -> transparent

Stuart commented on my last post – explaining how in the long run people will adjust to the new way and we’ll still get to have our cake (be much more transparent) and eat it (get some bang around milestones like beta release) too.  What he said is key and is the thing I keep…

2

Upcoming Whidbey beta

Eeesh, more than a month since I last posted.  I got feedback in the past couple days ago that while the community drops/more frequent builds are nice, what many people (especially non-MSDN subscribers) want is access to any build period.  The feedback is to work on that first, and more specifically to get our Whidbey beta out and…

5

Followup to post re: community preview philosphy

Thanks for the comments/feedback I received.  A few additional comments (I’ll try to keep this one short, or at least shorter). Josh Ledgard  questioned the need for every/daily builds.  I use the word “every” to make a couple points, one internally and one externally.  The internal point is that “shipping” these builds – with all…

11

Long-term goals/challenges of community tech previews

I was forwarded a great email thread from VB customers.  Here are some excerpts (from multiple people):   “I’m beginning to think “Community Editions” of products as large and complicated as Whidbey are NOT a good idea. Yes I said, NOT. Reason? I believe the average non-NDA, Joe Blow developer (esp. those new to .NET…

17

MS Openness and MVPs/RDs/trainers/authors…

I just happened across this blog post from Randy Holloway (http://weblogs.asp.net/rholloway/archive/2003/11/04/35707.aspx)   I’ve been thinking about this from a slightly different perspective.  As we do a better job in being open with information about upcoming products, responding to feedback, getting bits out earlier, I wonder how it impacts our “special” customers – MVPs, RDs, writers,…

8

Tech Preview stability, risk of wasting time, and CDs

I had the following exchange with a customer via email earlier today.  I thought it would be of general interest (thanks to Richard for letting me post this).  It explains some of the behind-the-scenes thinking around the Tech Preview, how it relates to our internal builds and external betas, where we want to go with…

10

P2P redistribution of Technical Preview

A couple people suggested p2p mechanisms as a way to enable downloads for anyone, and asked about restrictions on copying in the EULA.  Offhand, P2P seems like a great solution here, and I’ve started a thread with our legal department about making it so the EULA doesn’t preclude it.  It’s going to take a while…

5

March Technical Preview and non-MSDN subscribers

I received a question asking how/if people who aren’t MSDN subscribers can get this build.  Unfortunately, we do not yet have a way to enable this.  The issue is really one of not figuring out the logistics yet – we want to do this.  There are two (obvious) approaches – some kind of media fulfillment process…

6

Visual Studio 2005 Technical Preview March 2004

… also known as Whidbey.  People are starting to get this – some got it at VSLive/MDC, MSDN subscribers can download it now, and we’re in the process of manufacturing and shipping media to alpha participants, MVPs and PDC attendees (should start showing up over the next week).  This is not beta-quality.  We run weeks…

6