[sims] Capita Patch Management

[JJEuropa]

Is anyone else still as frustrated as i am over the Patch Management/Release process? A number of years ago a new appointment was made by Capita in order to improve the management and release of patches and with this came a promise that if a patch was current it would automatically be available for release. I think the process for this hasn't improved at all, if anything it's now taking longer to receive the requested patches.

 

Having to constantly, yes constantly, request patches be made available is a waste of our time, clients time and the support staffs time at Capita. I have been waiting for one patch to be made available in SOLUS3 since the 14th of February, it really doesn't need to be this time consuming!! Does it?

 

JJ

Edited February 28, 2014 by JJEuropa

[zag]

Its simply an effect of their software getting so bloated and complicated.

 

I'm not surprised they have huge issues with patches and upgrades to be honest.

 

To be fair, most of the patches I've used have done the job.

[JJEuropa]

Oh you're right, once you can get the patches they do the job, it's just getting them....

[vikpaw]

It shouldn't be that bad, i'd speak to your account manager or equivalent if you have one, or someone high up.

 

The problem with patches is that they are patches, so they can't just dish them out willy nilly, they should only go to the school's that need them to solve an issue. So somebody needs to manually vet them, and hopefully this has a formal logging system somewhere. More so when these are site specific issues, which seems to happen quite a lot, due to the bloating and widely different setups out there.

 

When they are rolled in to a full release and have been tested for all scenarios, it's no so bad, and at that point, you get a whole load at once.

[PhilNeal]

If you'd like to drop me an email with details I will follow up.

 

I'm aware that occasionally a patch is issued to fix a particular issue that doesn't make it into the next build because we are too far through the test cycle of the next release. We do not assume that a patch tested on the prior release will work on the next without going through a full test cycle.