Yes, it was all very tedious, and engineers were often faced with the brain-destroying task of comparing versions and figuring out what changed or not. There was no way to store the current version or go back to a previous version. There was only one version of the source tree, and if a bug in an older version was reported while they were in the midst of a significant change, the team would have to wait until that was done before looking for the bug - no matter how critical that bug was. Most teams had the crucial role of the librarian, in charge of merges and back-ups – which honestly doesn't sound like an entertaining job. After developing a feature, it would be merged back into the master copy. Each engineer started his source code from a clone of the master copy and then created his backups. Remember the times of floppy discs? For those under 30, they looked like this, and back in the earlier ages of the internet, they were the way people used to store information.Įvery project had a master copy, usually under one person's control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |