History of GNW Source Code
It never hurts to laugh a little.
The little disk drive that could
Once upon a time there was a small little disk drive that was asked to do a very very important job. This little disk drive had to be the gatekeeper for ALL the important source code of an up and coming internet monitoring company. This little disk drive knew what an honor this was and became determined to do everything in its power to protect this source code. He knew that there was nobody else out there to help him. He knew he had to go it alone. One day while this little disk drive was whirling away it ran into a very big mountain. It knew it had to climb this mountain in order to protect the source code. "I think I can, I think I can..." the little disk drive chanted. Suddenly, the earth shook, and the ground began to crumble from below. The little disk drive did the best it could to protect the source code but alas the disk drive fell from the mountain side tumbling over the crags of rock and crashed into the valley far below. Many people and much money was expended in order to revive the little disk drive, all to no avail. The source code was gone forever! The powers to be were frantic. They exclaimed "Help me!" Over time, several imposters appeared. Each imposter disk drive claiming to be able to help. Each one came to show off their marvelous source code. Each one appeared to resemble the little disk drive and indeed were able to imitate a large majority of the source code from the original little disk drive. But none were perfect. Each one was flawed. The powers to be were even more distraught now. So they devised a plan. They contemplated, wrestled, and discussed the various options. Eventually they all came to the same conclusion. We must use all the imposters! We must take the best attributes of each and build a NEW Disk Drive full of source code. Everyone worked feverously for a very long time. In the end everyone was satisfied and proud of the new disk drive.
The reality of the matter
The GNW source code repository was lost sometime in early 2005 due to a bad hard drive. There were no recent backups to be found. There was a CD found in the bank vault but the source code was way too old. Eventually there were 5 different "sandboxes" of the source code found on various machines around the GNW office. It was determined that they were from 4.1.1, 4.1.2, 4.1.3 and 188.8.131.52 source code trees. We spent a lot of time looking at the various trees of source code and could not determine that any one of them were the exact match to the software that was running in production.
So, we had a quandry. We decided to reconstitute the source code tree primarily from 4.1.3 and 184.108.40.206. It was determined that certain parts of 4.1.3 sandbox were more up to date than 220.127.116.11 and vice-versa. We called this new version of the source code 5.0.0.
We still have a quandry to this day. Every time a piece of the system requires a bug fix or enahncement, we have to build the 5.0.0 source code for that component and perform a black box test on it to ensure that it behaves exactly the same way as on production before we can even begin to "fix" the code. We cannot have any confidence in the validity of our 5.0.0 source code tree until every executable has gone through this exercise.
There have been several instances where the source code examined under the 5.0.0 tree does not match the behavior of the executables running in production. In those cases you must examine the differences between the source code of 5.0.0 against the various sandboxes use to re-constitute it. The various sandboxes can be found on the devserver box and are listed below.
/home/Pavan/srcBackup /home/Pavan/4.1.3 /home/Pavan/18.104.22.168 /home/Pavan/4.1.2 /home/Pavan/4.1.1
There is also a copy of this source code on the shared network drive. \\Kbase.globalnetwatch.com\gnw shared\ITTeamFolder\GNWSourceCode