Friday, March 03, 2006

Typical Release Friday

Today was a non-stop slam at work.

I got in at 7am and jumped on the emails from SVA answering my question about one of the J1939 functions that is beating me up. I spent the next hour trying to make my code work using their suggestions, but no good, it just won't work. But, buy this time it is 7pm on friday in Villingen, so no way I am getting more help on it.

Most of this time I had another co-worker who got the latest codebase for the XF/CF Cab controller who wanted help getting that opened up so that we could look into some of the stuff that they are doing.

After doing a build of my code I was fighting for time on our test buck so that I could do a quick run-through, but another co-worker was building up some truck parameter sets for the guys up at the tech center. As I was working on that, I remembered that I had a Software Readiness Review scheduled for after lunch... shit.

I spent the next hour co-ordinating bench test results from us, pete, and the tech center. I managed to break long enough to eat a UFO and stretch my legs.

I got back just in time for the review meeting, which I am in charge of now (my boss is kicking lots of responsibility down to me). I presented the test results to my boss and his boss and their equivelents at PB and PTC. After going over the results and talking over the high risk items, we decided to allow the software on the PTC House Trucks (if you live in western Washington you've probably seen these at some point).

After a good meeting, I was back to my desk to finish up the next rev of software. I spent two hours cleaning up the code, rebuilding it, setting up the default parameters, and packaging it up, and checking it into the revision control system. Then it was another half hour writing up the release email, cleaning up the change list, and sending that sucker out.

"Marty, I pulled the trigger! I'm out!"
"Good job this week, have a good weekend!"

Time to loosen the tie and relax...

(Oh, and not to mention the care taken in editing this post just right so that no NDAs get violated...)

No comments: