Software release control system and method

• US 5,950,209 A
• Filed: 10/02/1996
• Issued: 09/07/1999
• Est. Priority Date: 10/02/1996
• Status: Expired due to Term

• Current Assignee: Alcatel USA Sourcing L.P. (Nokia Corporation)
• Original Assignee: Alcatel USA Sourcing L.P. (Nokia Corporation)
• Inventors: Gillespie, R. John K., Carrier, David F. III, Weeks, Donald L. Jr., Lui, Janet Kwai Fun
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): Jung, David Yiuk
• Application Number:
  US08/724,830
• Time in Patent Office: 1,070 Days
• Field of Search: 707/1-206, 395/683-705, 709/101-106
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Source modules (160) are checked-into a version control subsystem (12) and check-in data are sent to the file release control system (10). System 10 provides for the selection of check-in data for attaching to a release form (162), the entry of additional information, such as a problem report number associated with the source module (160), and submission of the release form (162) for approval for a build (170) of a software product. System (10) further provides for the permanent identification (171) of versions of source modules (160) with a specific build (170) of a product.

Claims

1. A software release control method, comprising the steps of:

receiving and storing check-in data related to source modules checked into a version control system;

attaching selected check-in data to a selected release form;

submitting the selected release form for a build;

approving the build;

tagging source module associated with the check-in data attached to the release form of the approved build with a unique build label; and

building a load with source modules having the unique build label.

2. The method, as set forth in claim 1, further comprising the step of providing an interactive user interface for displaying information, prompting data entry by users, and receiving information associated with each of the steps.

3. The method, as set forth in claim 1, further comprising the steps of:

displaying a list of source modules checked into the version control system available for attachment to a release form; and

permitting the user to select from the displayed list, and receiving the selection as an input.

4. The method, as set forth in claim 1, further comprising the steps of:

displaying a list of release forms having check-in data attached thereto for submission; and

permitting the user to select from the list and receiving the selection as an input.

5. The method, as set forth in claim 1, further comprising the steps of:

displaying a list of submitted release forms for assignment to a build; and

permitting the user to select from the list and receiving the selection as an input.

6. The method, as set forth in claim 1, further comprising the steps of:

not approving the build; and

automatically sending an electronic notification message to one or more users associated with the source modules associated with the release form in the build.

7. The method, as set forth in claim 1, further comprising the steps of:

completing attachment of check-in data to release forms; and

automatically sending an electronic notification message to one or more users.

8. The method, as set forth in claim 1, wherein the attaching step further comprises the step of attaching check-in data of a third party software to a build.

9. The method, as set forth in claim 1, wherein the attaching step further comprises the steps of:

displaying a listing of third party software checked into the version control system;

permitting a selection of one or more third party software from the list; and

attaching check-in data of the selected third party software to a build.

10. The method, as set forth in claim 9, further comprising the step of retrieving the third party software from the version control system prior to building the load.

11. The method, as set forth in claim 1, further comprising the step of retrieving the source modules having the unique build label from the version control system prior to building the load.

12. The method, as set forth in claim 1, further comprising the step of associating a problem report number identifying a problem report with a source module being attached to a release form.

13. The method, as set forth in claim 12, further comprising the step of tagging the problem report with the unique build label.

14. The method, as set forth in claim 1, further comprising the step of formulating the build label as having an identification of a development stage for the load.

15. The method, as set forth in claim 1, further comprising the step of receiving a trigger from the version control system in response to a source module being checked in.

16. The method, as set forth in claim 1, further comprising the steps of:

displaying a list of source modules checked into the version control system available for attachment to a release form;

permitting the user to select from the displayed list, and receiving the selection as an input; and

prompting for and receiving user entry of information related to the selected source module.

17. The method, as set forth in claim 1, further comprising the steps of:

checking in a source module into a second version control system located at a remote site; and

receiving and storing check-in data from the second version control system related to the remotely checked-in source modules.

18. The method, as set forth in claim 17, further comprising the steps of:

remotely attaching selected check-in data to a selected release form; and

remotely submitting the selected release form for a build.

19. The method, as set forth in claim 17, further comprising the step of receiving source module change data from the second version control system.

20. The method, as set forth in claim 17, further comprising the step of tagging source module stored at the second version control system and associated with the check-in data attached to the release form of the approved build with a unique build label.

21. The method, as set forth in claim 1, further comprising the step of providing users multiple levels of authorized access and functions.

22. A software release control method, comprising the steps of:

receiving and storing check-in data related to source modules checked into a version control system;

selecting one or more check-in data;

attaching the selected check-in data to an open release form;

specifying one or more problem report numbers associated with the release form;

submitting the release form;

assigning the release form to a build;

tagging source modules associated with the check-in data attached to the release form in the build with a unique build label;

selecting one or more check-in data of any third party software; and

building a load with source modules having the unique build label.

23. The method, as set forth in claim 22, further comprising the step of providing an interactive user interface for displaying information, prompting data entry by users, and receiving information associated with each of the steps.

24. The method, as set forth in claim 22, further comprising the steps of:

displaying a list of source modules checked into the version control system available for attachment to a release form; and

permitting the user to select from the displayed list, and receiving the selection as an input.

25. The method, as set forth in claim 22, further comprising the steps of:

displaying a list of release forms having check-in data attached thereto for submission; and

permitting the user to select from the list and receiving the selection as an input.

26. The method, as set forth in claim 22, further comprising the steps of:

displaying a list of submitted release forms for assignment to a build; and

permitting the user to select from the list and receiving the selection as an input.

27. The method, as set forth in claim 22, further comprising the steps of:

not approving the build; and

automatically sending an electronic notification message to one or more users associated with the source modules associated with the release form in the build.

28. The method, as set forth in claim 22, further comprising the steps of:

completing attachment of check-in data to release forms; and

automatically sending an electronic notification message to one or more users.

29. The method, as set forth in claim 22, wherein the attaching step further comprises the steps of:

displaying a listing of third party software checked into the version control system;

permitting a selection of one or more third party software from the list; and

attaching check-in data of the selected third party software to a build.

30. The method, as set forth in claim 22, further comprising the step of retrieving the third party software from the version control system prior to generating the load.

31. The method, as set forth in claim 22, further comprising the step of retrieving the source modules having the unique build label from the version control system prior to building the load.

32. The method, as set forth in claim 22, further comprising the step of tagging the problem report with the unique build label.

33. The method, as set forth in claim 22, further comprising the step of formulating the build label as having an identification of a development stage for the load.

34. The method, as set forth in claim 22, further comprising the steps of:

displaying a list of source modules checked into the version control system available for attachment to a release form;

permitting the user to select from the displayed list, and receiving the selection as an input; and

prompting for and receiving user entry of information related to the selected source module.

35. The method, as set forth in claim 22, further comprising the steps of:

checking in a source module into a second version control system located at a remote site; and

receiving and storing check-in data from the second version control system related to the remotely checked-in source modules.

36. The method, as set forth in claim 35, further comprising the steps of:

remotely attaching selected check-in data to a selected release form; and

remotely submitting the selected release form for a build.

37. The method, as set forth in claim 35, further comprising the step of receiving source module change data from the second version control system.

38. The method, as set forth in claim 35, further comprising the step of tagging source module stored at the second version control system and associated with the check-in data attached to the release form of the approved build with a unique build label.

39. The method, as set forth in claim 22, further comprising the step of providing users multiple levels of authorized access and functions.

40. A software release control system, comprising:

a load builder coupled to a version control system and at least one developer workstation, the version control system having a database for storing source modules;

a check-in database accessible by the load builder for storing check-in data generated as source modules are being checked into the version control system, the check-in data having information related to each source module; and

a build database accessible by the load builder for storing data related to source modules that are approved for inclusion in a load, the stored data further associating the source modules stored in the version control system to the load.

41. The software release control system, as set forth in claim 40, wherein the build database comprises a submitted file for storing check-in data associated with source modules submitted for a build.

42. The software release control system, as set forth in claim 40, wherein the build database comprises an approved file for storing check-in data associated with source modules submitted and approved for a build.

43. The software release control system, as set forth in claim 40, wherein the build database comprises a deferred file for storing check-in data associated with source modules submitted for a build but not approved for an immediate build.

44. The software release control system, as set forth in claim 40, further comprising an access path to problem reports stored in a problem reporting tool.