[RESOLVED] Raising the bar for fixes to legacy compiler (and planning for 2005 SP2)?

[Ted.]

As the bar has raised as to what bugs are being considered for fix ( for those who haven't read, please see: http://blogs.msdn.com/vcblog/archive...30/610989.aspx )

what is the choosing strategy for service packs with respect to the compiler? As SP1 for Visual C++ 2005 had a very short dev cycle and has already been closed down, can you give information on whether the following bug fixes are included in SP1 (e.g. of performance regressions and customer vote count)

http://connect.microsoft.com/VisualS...edbackID=98890

http://connect.microsoft.com/VisualS...dbackID=101419

or the libraries?

http://connect.microsoft.com/VisualS...edbackID=98737

Would it be a useful process to circulate a list of fixes being considered for SP1 for about a week so others externally can look at the list and see if anything's missing?

What exactly is the strategy for SP2 in planning? Will Orcas effectively be SP2? (just as 2005 was effectively SP1 of 2003 since the window of usefulness of releasing an SP for 2003 has long since passed)