Login:
Password:

Yukon, Whidbey Releases Pushed to 2005

By Nate Mook and David Worthington, BetaNews

March 10, 2004, 10:31 PM

The Yukon wave of products has been pushed back and will not crest until next year. Microsoft has confirmed that two critical components on its future product roadmap, Whidbey and Yukon, have slipped into the 2005 timeframe.

The delay of Whidbey and Yukon will likely disrupt Redmond's closely tethered portfolio of products. As a result, Microsoft must now change tact and revise the release schedules of some of its principal product lines; giving credence to rumors that its upcoming Longhorn release of Windows may not meet its early 2006 target release date.

Other products possibly affected by the move include "Orcas," code-name for a future release of Visual Studio; Office 12, the Longhorn release of Office; and enterprise server products that rely on Yukon storage technologies and the Whidbey backend for developers.

While customers and ISVs wait out the commotion and uncertainty surrounding Longhorn's release date, service packs and interim releases of Windows XP and Windows Server 2003 are expected to fill the void.

As the delays mount, however, customers enrolled in Microsoft's Software Assurance program, which delivers regular code updates at set intervals, must be mindful. The impact of operating systems on the Software Assurance Program has historically been low, as many customers choose not upgrade, but Longhorn will bring a new level of interdependence between products.

"Yukon and Whidbey are rest stops on the road to Longhorn. Microsoft can't realistically begin serious Longhorn testing until both products ship," Jupiter Research senior analyst Joe Wilcox told BetaNews. "At the same time, certain Longhorn technologies must reach a certain level of development before Yukon and Whidbey can ship."

"Customers whose SA contracts for SQL Server or Visual Studio .Net expire next year wouldn't be eligible for upgrades if they came after the contracts expired. Customers would have to renew for the upgrades," said Wilcox.

Tom Rizzo, Microsoft Director of Product Management for SQL Server downplayed the affect Yukon's delay will have on other products, stating that Yukon is only a piece of the overall picture. "These products are not totally interdependent," said Rizzo.

But Jupiter's Wilcox questioned how quickly Microsoft will get Longhorn out the door. "A year ago, some folks laughed at the idea Microsoft would take as long as 2006 to ship Longhorn. Now, 2007 seems almost reasonable. Considering the huge impact Windows XP Service Pack 2 will likely have on existing software and customer behavior, Microsoft and its business customers will have plenty of distraction dealing with the current OS."

The final Yukon release of SQL Server is expected to ship in the first half of 2005 after a third "release candidate quality" beta ships later this year.

Add a Comment (8 Comments)

BetaNews reserves the right to remove any comment at any time for any reason. Please keep your responses appropriate and on topic. Foul language and personal attacks will not be tolerated.

Name (required):

E-mail (required):

Enter Your Comment:

By utomo

posted Mar 10, 2004 - 10:48 PM

It is not a good news.

Many developer waiting for this new visual studio, and they postponed to buy visual studio 2003/2002 for this reason.

I suggest Microsoft offering Whidbey (Visual Studio 2005) presales. so user can buy Whidbey, but they can use the old Visual Studio 2003 or 2002 before the product (Whidbey) arrive.
and when the Whidbey (Visual Studio 2005) is Final they get this license of Visual Studio 2005 without upgrade cost.
Without this microsoft will be leaved by many developer. they will not buy the products and then in short term they must pay the upgrade price which is not cheap.
Many developer will choose to move to another programming language.

Score: 0

By rodgerdb

posted Mar 10, 2004 - 11:11 PM

I tend to agree with utomo to some degree. It would be a good move on Microsoft's part to allow pre-sales with free upgrades to Whidbey final. It makes no sense not to offer this as it still gives companies and developers that wish to go .NET a small assurance on the next upgrade.

I don't believe that people will switch languages however. Current C#/ASP.NET is still very powerful. What Whidbey offers is to simplify and expand on some of what is done more manually in current offerings. So I believe using the current line is still reasonable.

Any other insights or opinions to this?

Score: 0

By utomo

posted Mar 11, 2004 - 2:35 AM

Hi Rogerdb,

Mostly developer now use Vb .net and Java, and C++.
Do some searching and you will find that many Vb developer moving to Java or other.
If they need to wait for long time, they will consider to move to others which is better.
There will be major changes, so maybe the code from VS 2003 need many modification to go to VS 2005. it is not good as already happend in VS 6 to 2002.
.net framework also will become 2.0 instead of 1.2, so it is major update.
What do you feel when your code from 2003 need many modification to go to 2005 ? I think you feel bad about it. VS 2005 offering good thins if it is fulfill what is explained in the roadmap and in some discussions.
but what I feel it is still not enough. it must adding more code for general purpose/most used application developments, so developers jobs become more easier. they just need to think about the process and the important parts, and visual studio will handle the dirty works. many developer will happy with this :)

Score: 0

By rodgerdb

posted Mar 10, 2004 - 11:12 PM

Actually I feel bad for having just posted that last comment. I assumed people are using C#. This is not necessarily the case. There are many VB.NET, C++, and other developers out there.

Sorry, no offense was meant to any developers.

Score: 0

By Neoprimal

posted Mar 11, 2004 - 5:54 AM

I am not at all into programming, though I'm upcoming IT and will have to deal with it. But you don't have to shred words or dumb anything down for me :)
I wanted to ask you guys something - especially utomo. Would it really be that easy for programmers to jump over to another language as you say? I had always thought that VB.net, C++ and the MS offered solutions were more robust compared to anything out there WITH REGARDS to MS OSs and such. Java and pearl and those I figured were excellent for multiplatform dealings. I know they are powerful too, I'm not sure if pearl is so much a programming solution, I always considered it more - html type programming than software programming, but I've heard different.

But ok - say MS went out of it's mind and introduced 2010 for the release date for whidbey.....what solutions do you think programmers would definately turn to - and what would that mean for them, and for the customers buying the products?

Score: 0

By wnowak1

posted Mar 12, 2004 - 10:54 AM

to add a note regarding perl. perl is more than just an html type programming language. It is very powerful and many routine tasks are written in perl on the *Nix platform. The first dvd decripting software, DeCSS was written in perl. Take a look at this:

http://www.bbc.co.uk/dna/h2g2/alabaster/A642999

Score: 0

By fewt

posted Mar 14, 2004 - 7:20 AM

Perl has become powerful enough that several highly visible applications have been written using it. IE: DVDRip

Score: 0

By wnowak1

posted Mar 12, 2004 - 10:48 AM

If you know a language such as C or C++ then learning another language is very easy. Knowing these two makes it very easy to learn for example java, or php, etc since the fundemantals are generally the same.

Score: 0