Lather, rinse and release

We had a Toolkit release last week and our product support medium, the forums, gave us instant feedback. So what happens when issues in the Toolkit prevent our customers from taking full advantage of it and block their core scenarios? We do not have service packs delivered 3 months after we release; that is way too late. After all, we release every couple of months which means that our response needs to be pretty quick. We follow up with a refresh release that patches the problems. Shawn Burke has a detailed blog post that provides an overview of the Toolkit processes and should help clarify any doubts you have. We hope to make the functioning of the Toolkit even more transparent in the future.

Motivations behind this 10618 release:

• A Tabs naming container issue that prevented users from finding child controls successfully
• A design time binary dependency that was accidentally being required on the deployment server because of web configuration file reference issues
• FilteredTextBox control was misbehaving when using navigation and control keys and
• The ToolkitScriptManager feedback needed to be incorporated

If you are already a Toolkit user then upgrading to the latest version of the Toolkit is straightforward. Ping us if you run into any issues.

One of the core tenets of Agile development is customer satisfaction by rapid, continuous delivery of useful software. We hope that we are living up to it!

Comments

• Anonymous
  January 01, 2003
  We releases a Toolkit Refresh (10618) on Monday to address some issues we missed with the 10606 build,