If you happened to follow the thread about the Feature Freeze project, you saw that we got into a good discussion about what things take time when working on complex parts.  (I know what you're thinking -- "everything" -- but those of us in the fixing-problems business need to narrow it down a little. )

The goal of this thread is to understand what's contributing to slowdowns (when they occur) and what can be done about it.  I'm not promising miracles here, but by understanding more about what you're actually running into, we can insure that we're working on the right problems.  We may also figure out some best practices that speed things up.  What I can promise is that we'll take all (constructive ) feedback seriously, and as we investigate more we'll give you an honest assessment of what we think we can and can't fix.

As the research continues, we'll probably ask various questions here and also post more formal surveys.  But to get things started, I'd like to follow up on an issue that was raised in the Feature Freeze discussion: "stuck" rebuild flags on part features.  Obviously, if a feature near the top of the tree thinks it needs to rebuild all the time, that's going to cause us to build a lot of features needlessly, wasting time.  However, a search through our database of customer-reported issues found very few reports of this, and they were pretty obscure situations.  So the question is:  Do you frequently run into features where the rebuild flag is stuck on (i.e. doesn't go away after rebuilding)?  If so, can you post some of these parts (or send them to us privately)?

Thanks,
Mark