According to the Product Family Life-Cycle Guidelines for Visual Basic 6.0 published by Microsoft, mainstream support for VB6 will cease by end of this month. Although it is common for a product to have its natural lifespan, I think this should come a little bit later. They should have given developers more time to migrate over to .NET (or VB.NET for that matter).
I believe VB6 is still widely used and quite prominent in the industry. Although, some people labeled it as the "kid's language", I believed it has contributed to a lot of useful applications in the industry - some powering banks and other critical applications. VB.NET is like a "grown-up's" language now. Every VB developer will need to know OO (which is a good thing) when they start with VB.NET.
VB.NET is a good advancement over VB6 and it will kick more @$$e$ when it hits Visual Basic 2005 - the .NET Framework 2.0 version. It will be on par with C# with operator-overloading, iterators and generics - a first class citizen of .NET.
Anyway, the news doesn't really impact me - we still have apps running on VB3 and the customers are happy with it. But if you want to do something for good-old VB6, voice it out here.