Vincent McDonald

Developer Support - hot fixes, Knowledge Base articles, and general support information
Hot Fixes Delayed - March-April 2008

The hot fixes previously scheduled for late March for NetAdvantage for .NET, TestAdvantage for Windows Forms (HP-QTP), and NetAdvantage for JSF have all been delayed until April 4.  There remains a possibility of further delays for any or all three of these hot fixes, though we are working diligently to avoid any further delays.  I will provide additional updates as the information becomes available.

Posted: 31 Mar 2008, 13:46
Filed under: , , ,

Comments

Jason Lockridge said:

Vince,

You realize, of course, that we rely on your commitment to a time frame when our customers are relying on our commitments.

-Jason Lockridge

# March 31, 2008 2:33 PM

vavan said:

again

# April 1, 2008 2:03 PM

Vincent McDonald said:

Jason,

We apologize for the delay in this hot fix.  We strive to deliver quality code to our customers, and sometimes this causes unforeseen delays.  I've raised your frustration to our Engineering department and we are doing everything we can to get this hot fix to our customers as soon as possible.

# April 2, 2008 4:34 PM

Jason Lockridge said:

Vince

Thank you so much for staying engaged in this blog.  The only way that these delays could be worse, if if we were getting no feedback from Infragistics about what is happening.  Such a case, though it would certainly cause us to find another vendor, would cause even greater uncertainty and stress in our development efforts.

Also, that IG would strive to deliver quality code must already be a given, or we would not be customers.  Given that as a given, it's not an explanation for delays.

I realize that the tilt of much of what I've written here and forums recently seems more than a little critical.  It is so only because I do expect better from a company with the stature and capacity that IG presents.  I set my standards for expectations from IG by judging your best work.  I've seen better than this from IG, and now I DO expect it.

That being said and understanding that we're not dealing in rocket science -- where deadline failure is not an option -- missed deadlines eat away at the core of trust that makes or breaks all companies.

Without wanting to sound too critical, I urge you and your engineering teams to set realistic and achievable deadlines that embrace reasonable delivery cycles.  The March 28 number came from IG.

There is already enough apparent slack in delivery in the presumed idea that *some* part of what you're doing *must* be ready, and is *holding* on the shelves while you ready everything else.  

For those of us with impatient customers calling us daily wondering why their contracts aren't being met, that's a bitter presumption to swallow.

# April 3, 2008 12:20 AM

Matthew Mulkey said:

Yes our customers are waiting on this hot fix as well.  Can I be notified as soon as this fix is ready for 7.2.

# April 3, 2008 1:27 PM

Vavan said:

April 7

Still no any fixes?

# April 7, 2008 9:04 AM

Vincent McDonald said:

We weren't able to release the hot fixes this past Friday.  We're still working out some additional details before we'll have a better idea on a revised release date.

Thank you all for your patience.  I'll provide additional information as a new post in my blog as soon as I can.

# April 7, 2008 10:00 AM

Vincent McDonald said:

We had a major technical issue last week. Microsoft has helped us through the issue, which is now resolved.

# April 7, 2008 2:26 PM

Matthew Mulkey said:

Now that it is resolved will this be released today?

# April 8, 2008 8:38 AM

Vincent McDonald said:

The comment you're referring to seems to be an incomplete traceback.  It's only the first few words of another blog post I've made about the next hot fix.  Refer to this other post for more information.

# April 8, 2008 8:43 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS