Hi Martin, Martin Paul wrote: Hi Don,Not possible or desirable. The patch deliverables cannot be changed once a patch is submitted for testing. This is to ensure that we test what we release and release what we test. This also ensures that only one version of any given patch can exist. This is one of the fundamental rules regarding our release management. This is an option that we are investigating. The problem we face is that our process needs to be extremely robust, so any solution that we try to put in place is future-proof as well as backward compatible, so nothing gets broken (or abused down the line, leading to further complications). In addition, we need to be very careful that all the systems that use the patch metadata we generate (eg. Oracle Enterprise Manager Ops Center, smpatch, MOS) do not get negatively impacted by any changes we make. What I'm trying to convey is that it is not just a case of seeing a problem and putting something in place to fix it; we need to look at the problem from all angles and patchdiag is only one small cog in the wheel. Best, -Don
--
![]() Don O'Malley Manager,Patch System Test Revenue Product Engineering | Solaris | Hardware East Point Business Park, Dublin 3, Ireland Phone: +353 1 8199764 Team Alias: rpe_patch_system_test...@oracle.com |
- Re: [pca] Non-existing patch Thomas Gouverneur
- Re: [pca] Non-existing patch Martin Paul
- Re: [pca] Non-existing patch Thomas Gouverneur
- Re: [pca] Non-existing patch Martin Paul
- Re: [pca] Non-existing patch Thomas Gouverneur
- Re: [pca] Non-existing patch - patchdia... Don O'Malley
- Re: [pca] Non-existing patch - pat... Martin Paul
- Re: [pca] Non-existing patch Michele Vecchiato
- Re: [pca] Non-existing patch Don O'Malley
- Re: [pca] Non-existing patch Martin Paul
- Re: [pca] Non-existing patch Don O'Malley