The difficulty with making individual fixes available is that the release cycle has a big overhead (mainly testing but also release notes, providing information across th company and customer base, updating CDs etc). So working on a release cycle means that we fix more bugs overall. That's why pretty much all packaged software companies work this way. Having said that, the number of bugs fixed in the next maintenance release will be much lower than in v9.0.4 so I don't expect to have to wait months for it.
We're slightly vague about timings because we are trying not to compromise testing. Setting a fixed timeframe tends to encourage poeple to cut corners, if we run late.
It might be worth making a couple more snapshots available to product management for testing. That way, we can increase the chances of the fix working across all of your clients.
Hope that all makes sense.
Chris
We're slightly vague about timings because we are trying not to compromise testing. Setting a fixed timeframe tends to encourage poeple to cut corners, if we run late.
It might be worth making a couple more snapshots available to product management for testing. That way, we can increase the chances of the fix working across all of your clients.
Hope that all makes sense.
Chris
Comment