That's a fairly typical software delivery schedule, though. Code freeze would've happened a couple/few months ago. Only showstopper bugs would have been fixed in the beta/RCs, with the rest falling into the service pack.
Only in an ideal world. I'm currently fighting a situation where dev was given full access (including root, over our objections) to the systems that are intended to be production, in addition to the dev systems. They've been unable to successfully port their code between the two (oh, and THEY had mismatched Oracle versions between the two environments, with dev at 10.1 and prod at 10.2). So, now that they've gotten rid of three of the morons involved, we're supposed to get the QA environment rebuilt to the same patch levels as dev (we patched them a week ago, now we have to back that out, the QA systems have sat idle for months, not even an Oracle install on them) AND get Oracle installed and configured AND get the application installed and working in two weeks.
We've already found hardcoded server names in the HTML source for one of the pages (the login page) while troubleshooting performance issues. I've already had one server barf trying to back out the patches, so I'm rebuilding it now from jumpstart (however, it had been patched at least once since the image was created), then I'll be reinstalling Veritas clustering. My boss has stated that we will leave the second database node at the patched level, with this rebuilt node as a fallback if there are issues getting things working on the higher patch level.
We saw this train wreck coming two years ago, but nobody listened to our objections. Now, they're using the same flawed decision making, absent some of the previous players, in the hopes of producing something better.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
The defense rests.
no subject
no subject
We've already found hardcoded server names in the HTML source for one of the pages (the login page) while troubleshooting performance issues. I've already had one server barf trying to back out the patches, so I'm rebuilding it now from jumpstart (however, it had been patched at least once since the image was created), then I'll be reinstalling Veritas clustering. My boss has stated that we will leave the second database node at the patched level, with this rebuilt node as a fallback if there are issues getting things working on the higher patch level.
We saw this train wreck coming two years ago, but nobody listened to our objections. Now, they're using the same flawed decision making, absent some of the previous players, in the hopes of producing something better.
no subject