This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
My point is we can wait for MONTHS before knowing about an SPR that might be ultra-important
My main point was that, as a customer, you get access to some SPR knowledge earlier if there are Fix Packs being constructed.
For example, unless there's a FP being made for 8.5.0, we won't know about any known SPRs for it until 8.5.1 starts becoming populated in the Fix List database. Since 8.5.1 won't be out until August at the earliest, we won't see those SPRs until likely May/June at the earliest.
So for at least 5 months we've got 3 options:
1. Search for known SPR #s here
2. Hope we find any pertinent problem during testing. Then we have to open support tickets and support has to ID the problem (which means THEY'VE got to find the SPR #). If there's a hotfix, great, if not then then we have to decided if it's a ship-stopper on our end.
3. Discover a problem after rollout. Then we have to open support tickets and support has to ID the problem (again, they've got to find the SPR #). If there's a hotfix, good, but now we're talking about bringing production servers offline. What's worse is if there's NOT a hotfix, in which case we have to decide if now a rollback is necessary.
I'll agree that support is generally very good about hot fixes.
But if we at least had access to a list of known SPRs for 8.5.0 sooner then we could specifically test against them, helping us to open support tickets in scenario #2 as opposed to scenario #3.
This is especially important with .0 releases, since they are usually major upgrades with NAB view changes, etc.
For example, I've learned through this forum that 8.5.0 has several problems. Just off the top of my head:
- LS debugger sometimes doesn't work
- Designer is crashy
- DAOS bombs with high-strength encryption
- Adminp crashes (yes, this was addressed in HF1, but that's not listed in the Fix List database either. It's a "must have" I would think.)
Here's a better example:
Just today it looks like a "ship-stopper" from 8.0 (that was fixed in 8.0.1) has regressed in 8.5.0:
I hope that people catch this one during testing. If not, OUCH.
The problem will be SPRed if somebody reports it, but the rest of the world won't know unless/until it gets triaged into an FP and updated in the Fix List db. Until that point us AND Lotus support are wasting a lot of everybody's time.
Feedback response number ECBS7P8K23 created by ~Dana Elfreekony on 02/13/2009
My point is we can wait for MONTHS before knowing about an SPR that might be ultra-important
Return to top
. . . . My point is we can wait for MONTHS ... (~Sanjay Quettum... 13.Feb.09) 
