Patent application number | Description | Published |
20090259933 | System for Displaying an Annotated Programming File - A system includes a display, a processor executing an application program for displaying an annotation file, and memory storing program instructions of the application program. The processor associates an annotation with a programming module of a baseline file to display, in an unsegmented window of a graphical user interface, the baseline file as a hierarchical structure having nodes. Each node represents a programming module of the baseline file. Displayed is an annotation in the unsegmented window of the GUI proximate to the node that represents the programming module with which the annotation is associated. The displayed annotation includes selectable messages displayed proximate to each other to facilitate visual comparison. Each selectable message describes a modification made to the baseline file by a different contributor. The annotation indicates that the modifications produce a conflict. The conflict is resolvable within the unsegmented window by a selection of one of the selectable messages. | 10-15-2009 |
20120016867 | Displaying changes to versioned files - Presenting changes to versioned files. The method can include presenting a first view comprising a plurality of indicators, each of the indicators corresponding to a respective version of a file. A selection of a particular version of a file can be detected. A selection of another version of the file can be detected. In response to the selection of the other version of the file, the versions of the file can be compared to identify differences between the versions. Comparison information based on the differences can be generated. The comparison information can be filtered so that the comparison information fits within a second view having a desired size. | 01-19-2012 |
20120192141 | SELECTIVE NOTIFICATIONS ACCORDING TO MERGE DISTANCE FOR SOFTWARE VERSION BRANCHES WITHIN A SOFTWARE CONFIGURATION MANAGEMENT - A computer-implemented method of controlling version branching within a software configuration management system (SCMS) can include, responsive to a user initiating a check-out operation of a file within the SCMS, identifying the file and a workspace of the user and searching nodes of the repositories of the SCMS for a successor version of the file. When a successor version of the file is located within a node that is within a predetermined distance of the workspace of the user, a notification that the successor version of the file is within the predetermined distance of the workspace of the user can be output. When a successor version of the file is not located within a node within a predetermined distance of the workspace of the user, the file can be checked-out to the workspace of the user. | 07-26-2012 |
20120203768 | DISPLAYING CHANGES TO VERSIONED FILES - Presenting changes to versioned files. The method can include presenting a first view comprising a plurality of indicators, each of the indicators corresponding to a respective version of a file. A selection of a particular version of a file can be detected. A selection of another version of the file can be detected. In response to the selection of the other version of the file, the versions of the file can be compared to identify differences between the versions. Comparison information based on the differences can be generated. The comparison information can be filtered so that the comparison information fits within a second view having a desired size. | 08-09-2012 |
20130111441 | PARALLEL DEVELOPMENT OF A SOFTWARE SYSTEM | 05-02-2013 |
20130111442 | PARALLEL DEVELOPMENT OF A SOFTWARE SYSTEM | 05-02-2013 |
20130326478 | VERSION LABELING IN A VERSION CONTROL SYSTEM - Version labeling of an artifact in a version control system. An embodiment can include accepting at least one change set into a configuration for the artifact. Based on the change set, a new version of the artifact can be selected by the configuration. Via a processor, an identifier can be generated for the newly selected version of the artifact. The identifier can include at least a branch name for a branch in which the newly selected version of the artifact is contained and a sequence number for the newly selected version of the artifact. The newly selected version of the artifact can be labeled with the generated identifier. | 12-05-2013 |
20130326480 | VERSION LABELING IN A VERSION CONTROL SYSTEM - Version labeling of an artifact in a version control system. An embodiment can include accepting at least one change set into a configuration for the artifact. Based on the change set, a new version of the artifact can be selected by the configuration. Via a processor, an identifier can be generated for the newly selected version of the artifact. The identifier can include at least a branch name for a branch in which the newly selected version of the artifact is contained and a sequence number for the newly selected version of the artifact. The newly selected version of the artifact can be labeled with the generated identifier. | 12-05-2013 |
20140101637 | SELECTIVE NOTIFICATIONS ACCORDING TO MERGE DISTANCE FOR SOFTWARE VERSION BRANCHES WITHIN A SOFTWARE CONFIGURATION MANAGEMENT SYSTEM - A computer-implemented method of controlling version branching within a software configuration management system (SCMS) can include, responsive to a user initiating a check-out operation of a file within the SCMS, identifying the file and a workspace of the user and searching nodes of the repositories of the SCMS for a successor version of the file. When a successor version of the file is located within a node that is within a predetermined distance of the workspace of the user, a notification that the successor version of the file is within the predetermined distance of the workspace of the user can be output. When a successor version of the file is not located within a node within a predetermined distance of the workspace of the user, the file can be checked-out to the workspace of the user. | 04-10-2014 |
20140188852 | DISPLAYING CHANGES TO VERSIONED FILES - Presenting changes to versioned files. The method can include presenting a first view comprising a plurality of indicators, each of the indicators corresponding to a respective version of a file. A selection of a particular version of a file can be detected. A selection of another version of the file can be detected. In response to the selection of the other version of the file, the versions of the file can be compared to identify differences between the versions. Comparison information based on the differences can be generated. The comparison information can be filtered so that the comparison information fits within a second view having a desired size. | 07-03-2014 |
20140279975 | MANAGING VERSIONS OF ARTIFACTS STORED ACROSS DISPARATE TOOLS - Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool. | 09-18-2014 |
20140279980 | MANAGING VERSIONS OF ARTIFACTS STORED ACROSS DISPARATE TOOLS - Arrangements described herein relate to managing versions of artifacts stored across disparate tools. In a multi-dimensional configuration space, dimensions can be defined. The dimensions can represent respective variations of respective versions of a plurality of artifacts for at least a first configuration of a system. Via the dimensions, versions of the plurality of artifacts can be mapped to at least a corresponding first configuration of the system, the mapped versions of the plurality of artifacts corresponding to the versions of the artifacts used in the first configuration. The first configuration can be identified by a point in the multi-dimensional configuration space defined by the respective dimensions. At least a first of the plurality of artifacts can be stored by a first tool, and at least a second of the plurality of artifacts can be stored by a second tool disparate from the first tool. | 09-18-2014 |