Bugzilla – Full Text Bug Listing
| Summary: | [zOS] Package target copies wrong script for ACVersion.sh | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mike Reid <mikereid> | ||||
| Component: | TPTP | Assignee: | Mike Reid <mikereid> | ||||
| Status: | CLOSED FIXED | QA Contact: | Kathy Chan <kathy> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jcayne, jerome.bozier, jgwest | ||||
| Version: | unspecified | Flags: | kathy:
pmc_approved?
(oec) kathy: pmc_approved? (ernest) kathy: pmc_approved+ jgwest: pmc_approved+ jerome.bozier: pmc_approved+ jcayne: review+ |
||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | other | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Mike Reid
Created attachment 188251 [details]
Patch
Patch attached that copies the correct file.
Joel, can you review patch? Patch looks good. I would like to request that the following defect be considered for PMC approval for 4.7.2. 1. Explain why you believe this is a stop-ship defect. How does the defect manifest itself, and how will users of TPTP / consuming products be affected if the defect is not fixed? If a user on a downstream product supporting zOS tries to execute 'ACVersion.sh', it will stop the running AC instead of reporting the version number, potentially interrupting a profiling session or other work. This is a bad usability flaw for the user, particularly if a profiling session is in progress. 2. Is there a work-around? If so, why do you believe the work-around is insufficient? A user can manually invoke 'ACServer -v' after setting appropriate environment variables, but they have no way of knowing to do this until they discover the problem first-hand. 3. Is this a regression or API breakage? Explain. No, this behaviour seems to be in older releases as well. 4. Does this require new API? No. 5. Who performed the code review? Joel Cayne. 6. Is there a test case attached to the bugzilla record? n/a 7. What is the nature of the fix? What is the risk associated with this fix? Packaging change. Low risk; only platform affected is zOS. 8. Is this fix related to any standards that TPTP adheres to? If so, who has validated that the fix continues to adhere to the standard? No. Requesting PMC approval for TPTP 4.7.2. Checked into HEAD w/ PMC approval. Resolving. Closing. |