Version control system for geographically distributed software development

• US 5,675,802 A
• Filed: 03/31/1995
• Issued: 10/07/1997
• Est. Priority Date: 03/31/1995
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: Pure Atria Corp. (International Business Machines Corporation)
• Inventors: Minard, Debra A., Kane, Kenneth P., Fernandez, Gary L., Allen, Larry W., Leblang, David B., McLean, Gordon D. Jr.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Min, Donald
• Application Number:
  US08/414,575
• Time in Patent Office: 921 Days
• Field of Search: 395/600, 395/608, 395/617, 395/619, 395/703, 395/712
• US Class Current: 717/103
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A data processing system and method for controlling files at a local development site within a geographically distributed multisite software development project includes a storage device, a processor, a mastership enforcer and an exchanger. The storage device stores a local replica including a plurality of files. Each file comprises a plurality of branches, and each branch comprises a plurality of versions of the file. The processor executes instructions, and retrieves and stores versions of the files in the storage device. The mastership enforcer provides the processor with the exclusive capability to modify specific branches by adding new versions of target files as determined by multisite mastership rules. The processor can create new versions of the target files, which are stored in the local replica within the storage device. The exchanger periodically updates the local replica by exporting the new versions of the target files to remote replicas at geographically remote development sites and importing additional new versions of the files from remote replicas. Thus, different branches of files, which are stored in multiple replicas geographically distributed at various development sites, can be modified concurrently and the replicas are updated with each others modifications periodically, without losing modifications or allowing inconsistent modifications among the replicas.

Claims

1. A data processing system for controlling files at a local development site within a geographically distributed multisite software development project including remote development sites, comprising:

a storage device for storing a local replica comprising a plurality of files, each file comprising a plurality of branches, each branch comprising a plurality of versions of each file,

a processor for executing instructions and retrieving versions from and storing versions to the storage device,

a mastership enforcer for (i) providing the processor with the exclusive capability to modify specific branches by adding new versions of target files and (ii) preventing the processor from modifying other branches, as determined by multisite mastership rules, and

an exchanger which periodically updates the local replica by exporting the new versions of the target files to remote replicas at remote development sites and importing additional new versions of the files from remote replicas.

2. The data processing system of claim 1 wherein the local replica further comprises meta-data which is associated with one or more files, branches or versions, wherein the mastership enforcer provides the processor with the exclusive capability to modify specific types of target meta-data as determined by multisite mastership rules, wherein the exchanger periodically updates the local replica by exporting the modified target meta-data to the remote replicas and importing additional modified meta-data from the remote replicas.

3. The data processing system of claim 2 wherein the mastership enforcer provides the processor with the capability to modify only (i) types of meta-data designated as being under full control of the local development site or (ii) types of meta-data designated to be under distributed control and attached to a file, branch or version that is modifiable at the local development site.

4. The data processing system of claim 2 wherein the mastership enforcer is capable of reassigning the exclusive capability to modify the specific types of target meta-data to a remote development site.

5. The data processing system of claim 2 wherein the mastership enforcer is capable of reassigning the exclusive capability to modify the branches or specific types of meta-data to a remote development site when the exchanger periodically updates the local replica.

6. The data processing system of claim 2 wherein the exchanger further comprises an exporter for exporting the new versions of the target files and meta-data to each remote replica, a transporter for transporting the new versions of the target files and meta-data to the remote replicas and an importer for importing additional new versions of the files and meta-data from the remote replicas.

7. The data processing system of claim 6 wherein the new versions of the target files and meta-data are transported over a data communications network or by magnetic tape.

8. The data processing system of claim 6 wherein the transporter is customizable.

9. The data processing system of claim 2 further comprising a backup storage device for storing a backup copy of the local replica, wherein the local development site is restorable after loss of the local replica by restoring the backup copy of the local replica to the storage device and by importing missing files, branches, versions and meta-data from the remote replicas.

10. The data processing system of claim 9 wherein the local development site, after having restored the backup copy of the local replica, imports missing files, branches, versions and meta-data from the remote replicas as part of the periodic updating performed by the exchanger.

11. The data processing system of claim 1 wherein the mastership enforcer is capable of reassigning the exclusive capability to modify the branches to a remote development site.

12. The data processing system of claim 1 wherein the local replica further restricts the capability to modify each branch to a single user at a time at the local development site.

13. A method for controlling versions of the files at a local development site within a geographically distributed multisite software development project which includes remote development sites, comprising:

storing a local replica comprising a plurality of files in a storage device, each file comprising a plurality of branches, each branch comprising a plurality of versions of the file,

executing instructions and retrieving versions from and storing versions to the storage device using a processor,

providing the processor with the exclusive capability to modify specific branches by adding new versions of target files and preventing the processor form modifying other branches, as determined by multisite mastership rules, and

periodically updating the local replica by exporting the new versions of the target files to remote replicas at remote development sites and importing new versions of the files from remote replicas.

14. The method of claim 13, wherein the local replica further comprises meta-data which is associated with one or more files, branches or versions, further providing the processor with the exclusive capability to modify specific types of target meta-data as determined by multisite mastership rules, wherein the exchanger periodically updates the local replica by exporting the modified target meta-data to the remote replicas and importing additional modified meta-data from the remote replicas.

15. The method of claim 14 further comprising reassigning the exclusive capability to modify the specific types of target meta-data to a remote development site.

16. The method of claim 14 further providing the processor with the capability to modify only (i) types of meta-data designated as being under full control of the local development site or (ii) types of meta-data designated to be under distributed control and attached to a file, branch or version that is modifiable at the local development site.

17. The method of claim 14 further comprising periodically updating the local replica by exporting the new versions of the target files and modified target meta-data to each remote replica, transporting the new version of the target files and modified meta-data to the remote replicas, and importing additional new versions of the files and meta-data from the remote replicas.

18. The method of claim 17 wherein the transporting is customizable.

19. The method of claim 17 further comprising transporting the new versions of the target files over a data communications network or by magnetic tape.

20. The method of claim 14 further comprising reassigning the exclusive capability to modify the branches or specific types of meta-data to a remote development site when the exchanger periodically updates the local replica.

21. The method of claim 20 wherein the local development site, after having restored the backup copy of the local replica, imports missing files, branches, versions and meta-data from the remote replicas as part of the periodic updating performed by the exchanger.

22. The method of claim 14 further comprising storing a backup copy of the local replica in a backup storage device, wherein the local development site is restorable after loss of the local replica by restoring the backup copy of the local replica to the storage device and by importing missing files, branches, versions and meta-data from the remote replicas.

23. The method of claim 13 further comprising restricting the capability to modify each branch to a single user at a time at the local development site.

24. The method of claim 13 further comprising reassigning the exclusive capability to modify the branches to a remote development site.