May 28 - June 3

"build one to throw away"

duplicated the work I did on utforge02 last week onto utforge01 – this time I have the stack working with Subversion 1.6.11
developed RPM specifications for the following packages:
- clearsilver.spec
- mod_auth_eid-2.5.spec
- mod_fastcgi-2.4.6.spec
- mod_ipmagic-6.1.spec
- mod_python-3.3.1.spec
- mod_wsgi-2.5.spec
- python25-2.5.4.spec
- python25-django-1.1.spec
- python25-docutils-0.5.spec
- python25-genshi-0.5.1.spec
- python25-ldap-2.3.9.spec
- python25-openssl-0.9.spec
- python25-psycopg2-2.0.12.spec
- python25-setuptools-0.6c9.spec
- subversion-1.6.11.spec
discussions with Oliver related to best practices on building packages
user support, correspondence

software maintenance license for 2000+ users has been renewed until June 17, 2011
minor user support, correspondence

still waiting on StratComm to finish the new SLA service to change the UTForge SLA – received a message from Jen Jobst this week stating that the new tentative due date is June 18
need to decide whether I want to update the stack this weekend sans a maintenance window or after I get back from vacation – I am leaning towards the latter, but I would also like to finish the stack update and have the ability to move on to other tickets immediately when I return June 21

get multiple apache processes running on each production server – one dedicated to Subversion the other to Trac
will list more later today