Comment Re:Confused. (Score 2) 270
Have you ever worked in IT? Because I can assure you it's a lot more challenging than that.
You see, at 1 update/day for 50 days, you risk potentially breaking any application that the business uses. Every update is not just "rolling out Java", it's the following:
1. Hunt around for download links for a full, offline version of the installer.
2. Find out which management system you're going to use to do remote installs to every system.
3. Write up a change control document and follow an approval process to get changes out.
4. Test said update to a test environment as best as you can.
5. Get approval for update.
6. Roll out update to users.
7. If update breaks something, roll all users back.
8. Try to explain to management why IT just caused significant downtime.
You see, at 1 update/day for 50 days, you risk potentially breaking any application that the business uses. Every update is not just "rolling out Java", it's the following:
1. Hunt around for download links for a full, offline version of the installer.
2. Find out which management system you're going to use to do remote installs to every system.
3. Write up a change control document and follow an approval process to get changes out.
4. Test said update to a test environment as best as you can.
5. Get approval for update.
6. Roll out update to users.
7. If update breaks something, roll all users back.
8. Try to explain to management why IT just caused significant downtime.