Added by Susan McEvoy, last edited by Ryan Ordway on Aug 26, 2009  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Conflicts among various applications caused by upgrades (ie Ruby gems)
Also needing to keep current (Drupal is way behind)

Should Ryan make the decisions, move things forward, or should developers?
Terry - developer driven (but Ryan should track security patches)
Ryan could help manage, but he can't tell what would break

Apollo was on 1.86, not up on security patches - how much time do we need to move things forward
Developers will need at least a month
How easy is it to update the links to the software/patches? In industlry, install in parallel, developers switch as they can, switch back and forth. (For gems and rails, fine, but for Ruby, not possible, it's actually executed w/in a apache, it's only able to use a version of it. In theory, could have 2 version installed, but couldn't have them active. Ryan would have to make them active.

Apollo is where we try it first before moving to production

Server Software
Apache - kept up to date within current minor version (2.2)
Tomcat - locally managed

Programming Languages
PHP - kept up to date by OS within current minor version for security updates, bugs
Ruby - since we are using > 2.7, we have to manage security updates
Perl - kept up to date by OS within current minor version for security updates, bugs
Python coming - kept up to date by OS within current minor version

Web Applications
Drupal - locally managed
Confluence - locally managed
Jira - locally managed
Dspace - locally managed
WPMU - locally managed
Wordpress - locally managed
Lyceum - locally managed
Omeka - locally managed
ContentDM - locally managed, possibly hosting moving to UO

Locally Developed Applications
LibraryFind
Ala Carte
Oregon Explorer
MobileLibrary

Mailing lists give notifications - some have rss feeds - depends on the app
Can write script that would compare versions?

2 different things - development, as needed; security - pushed
Individual projects
Talk to whole group as new versions are available - give a month - can everyone be ready?

Agreed Process

1. Developer will request
2. Ryan will install - make a ticket and send out an email to whole group
3. 2 weeks to respond
4. Set due date a couple days before, send out notification when hits due date

0 Comments