Software release control system and method
First Claim
Patent Images
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 Assignments
0 Petitions
Accused Products
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.
-
Citations
44 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
-
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. - View Dependent Claims (23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39)
-
-
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. - View Dependent Claims (41, 42, 43, 44)
-
Specification