On 05/07/99 12:09:23 you wrote:
[process details snipped] We are just beginning to move to this new model. There is likely to be some overlap between P releases and maintenance releases in the near term. I hope you can bear with us as we work through this transition.
Well, the new process looks more efficient and sensible, but basically it amounts to eliminating P releases and putting out regular maintence releases. This is fine, but it doesn't really eliminate the problem this particular custoemr had. In the new scheme, CS would have given this customer a 5.2.1Dx patch which they'd be using when 5.2.2 came out. Due to the timing constraints you mention, the D patch might not have made it into the 5.2.2 release. The new customer, seeing 5.2.2 (either on a new filer or on NOW) assumes 5.2.2 would include 5.2.1Dx, and so downloads it and gets bitten.
This was what prompted me to suggest what I did before. In the new scheme you describe, since CS can spin a D release quickly to address a customer problem, when 5.2.2 is ready for release it can be delayed only a day or two for CS to spin any Ds it needs from 5.2.1 to go with 5.2.2 that didn't make it into 5.2.2. Then when the customer running 5.2.1Dx goes to NOW, they'll not only see 5.2.2, but 5.2.2Dx with a note only to download this version if they're running 5.2.1Dx.
Of course, if CS really can't spin a release that fast, then okay. But I suspect this might be what will wind up happening anyway. A customer experiences one bug, which CS fixes in 5.2.1Dx, then another bug which is fixed in 5.2.2. CS will have to spin a 5.2.2Dx release before 5.2.3 (which hopefully finally contains the 5.2.1Dx patch missing in 5.2.2)
I also agree with Paul regarding the rfe's. We need to do a better job of documenting the changes that go into these releases. Customers need accurate information about the content of these releases in order to make informed decisions in managing their filers. You should expect to see change here as well.
Yes, barring any other corrective action at least this will provide another way an otherwise confused customer can learn not to install a certain version because the patch they want isn't in it.
Bruce