CREATING A SUPERSEDING SOFTWARE RELEASE

• US 20120066669A1
• Filed: 09/14/2010
• Published: 03/15/2012
• Est. Priority Date: 09/14/2010
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: BOUZAKIS, JOHN, Motipara, Dhruti Ritesh, Rivera, Anais Graciela, Su, Kurt Chien-Hua
• Application Number:
  US12/881,639
• Publication Number:
  US 20120066669A1
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

A method, system, and computer usable program product for creating a superseding software product release are provided in the illustrative embodiments. A first set of metadata describing a set of parts related to a first release is received at an application executing in a computer. A second set of metadata describing a second set of parts related to a second release is received. Using the first and the second sets of metadata, a part to be added to the second set of metadata is identified such that the second release is sufficient to supersede the first release. The second set of metadata is updated to include metadata of the part such that an updated second release according to the updated second set of metadata is sufficient to supersede the first release.

Claims

1. A computer implemented method for creating a superseding release of a software product, comprising:

receiving, at an application executing in a computer, a first set of metadata describing a set of parts related to a first release;

receiving a second set of metadata describing a second set of parts related to a second release;

identifying using the first and the second sets of metadata a part to be added to the second set of metadata such that the second release is sufficient to supersede the first release; and

updating the second set of metadata to include metadata of the part such that an updated second release according to the updated second set of metadata is sufficient to supersede the first release.

2. The computer implemented method of claim 1, further comprising:

packaging a plurality of artifacts according to the parts in the updated second set of metadata to form the superseding release of the software product.

3. The computer implemented method of claim 1, wherein the part is deleted in the first set of metadata and added in the second set of metadata, further including:

sending an instruction to a repository to reset a delete attribute of an artifact associated with the part.

4. The computer implemented method of claim 1, wherein the part is deleted in the first set of metadata and deleted in the second set of metadata, further comprising:

sending an instruction to a repository to modify an attribute of an artifact associated with the part such that the artifact appears to have been deleted in the second release in the repository.

5. The computer implemented method of claim 1, wherein the part is a prerequisite part of another part in the first metadata, further comprising:

adding the part to the second set of metadata.

6. The computer implemented method of claim 1, wherein the second release is a proposed new release, the second set of metadata is a proposed manifest of the proposed new release, the proposed new release being insufficient to supersede the first release.

7. The computer implemented method of claim 1, wherein the first release is an intermediate release, wherein a set of metadata is a parts manifest, and wherein the set of parts of the first set of metadata includes a first subset of parts included in the first release, a second subset of parts deleted in the first release, and a third subset of parts that are prerequisites to the parts in the first subset.

8. A computer usable program product comprising a computer usable storage medium including computer usable code for creating a superseding release of a software product, the computer usable code comprising:

computer usable code for receiving, at an application executing in a computer, a first set of metadata describing a set of parts related to a first release;

computer usable code for receiving a second set of metadata describing a second set of parts related to a second release;

computer usable code for identifying using the first and the second sets of metadata a part to be added to the second set of metadata such that the second release is sufficient to supersede the first release; and

computer usable code for updating the second set of metadata to include metadata of the part such that an updated second release according to the updated second set of metadata is sufficient to supersede the first release.

9. The computer usable program product of claim 8, further comprising:

computer usable code for packaging a plurality of artifacts according to the parts in the updated second set of metadata to form the superseding release of the software product.

10. The computer usable program product of claim 8, wherein the part is deleted in the first set of metadata and added in the second set of metadata, further including:

computer usable code for sending an instruction to a repository to reset a delete attribute of an artifact associated with the part.

11. The computer usable program product of claim 8, wherein the part is deleted in the first set of metadata and deleted in the second set of metadata, further comprising:

computer usable code for sending an instruction to a repository to modify an attribute of an artifact associated with the part such that the artifact appears to have been deleted in the second release in the repository.

12. The computer usable program product of claim 8, wherein the part is a prerequisite part of another part in the first set of metadata, further comprising:

computer usable code for adding the part to the second set of metadata.

13. The computer usable program product of claim 8, wherein the second release is a proposed new release, the second set of metadata is a proposed manifest of the proposed new release, the proposed new release being insufficient to supersede the first release.

14. The computer usable program product of claim 8, wherein the first release is an intermediate release, wherein the set of parts of the first set of metadata includes a first subset of parts included in the first release, a second subset of parts deleted in the first release, and a third subset of parts that are prerequisites to the parts in the first subset.

15. The computer usable program product of claim 8, wherein the computer usable code is stored in a computer readable storage medium in a data processing system, and wherein the computer usable code is transferred over a network from a remote data processing system.

16. The computer usable program product of claim 8, wherein the computer usable code is stored in a computer readable storage medium in a server data processing system, and wherein the computer usable code is downloaded over a network to a remote data processing system for use in a computer readable storage medium associated with the remote data processing system.

17. A data processing system for creating a superseding release of a software product, the data processing system comprising:

a storage device including a storage medium, wherein the storage device stores computer usable program code; and

a processor, wherein the processor executes the computer usable program code, and wherein the computer usable program code comprises;

computer usable code for receiving, at an application executing in a computer, a first set of metadata describing a set of parts related to a first release;

computer usable code for receiving a second set of metadata describing a second set of parts related to a second release;

computer usable code for identifying using the first and the second sets of metadata a part to be added to the second set of metadata such that the second release is sufficient to supersede the first release; and

computer usable code for updating the second set of metadata to include metadata of the part such that an updated second release according to the updated second set of metadata is sufficient to supersede the first release.

18. The data processing system of claim 17, further comprising:

computer usable code for packaging a plurality of artifacts according to the parts in the updated second set of metadata to form the superseding release of the software product.

19. The data processing system of claim 17, wherein the part is deleted in the first set of metadata and added in the second set of metadata, further including:

computer usable code for sending an instruction to a repository to reset a delete attribute of an artifact associated with the part.

20. The data processing system of claim 17, wherein the part is deleted in the first set of metadata and deleted in the second set of metadata, further comprising:

computer usable code for sending an instruction to a repository to modify an attribute of an artifact associated with the part such that the artifact appears to have been deleted in the second release in the repository.