Wow, these two UBEs have been my package build buddies for a very long time. We’ve spent many a late night together, although I must admit we are generally joined by R98825D later in the night. R98825D always steals the show and does all of the glory work that has been set up by the rest. R98825F is relatively new to the scene and does not always get invited, but when it does – generally outstays their welcome. Oh yeah, and convincing R98825F to tip up the first time is pretty difficult.
Their eulogy (R9621 & R9622) could go on for days about how helpful they’ve been and perhaps it’d be quite tearful.
I hope their replacements are up to the task!
R9621S – Server Package Build
R9622C – Client package build
Of course, this is VERY confusing – as the R9621 used to be the client and the R9622 used to be the server. How did this change get through conceptual change management?
JM17096 is responsible for the introduction of these new players. This ESU was put on for the new tools, 9.1.5.2
2 comments:
Hi, I've just discovered this . I was almost going to open a SR before seeing your post. The new names are really disturbing . Do you think that is a "dev" mistake ?
I figured out the reason. Actually it's related to the sequencing of the batches .The first one is always 21 and the second is 22. In these tools the server build is done before the client. then they added S and C to avoid confusion. Not sure it really helps.
There may be probably better solutions to handle this.
Post a Comment