Version control and management

Patent metadata

Field	Value
Publication number	US-10180837-B2
Application number	US-201514803418-A
Country	US
Kind code	B2
Filing date	Jul 20, 2015
Priority date	Jul 20, 2015
Publication date	Jan 15, 2019
Grant date	Jan 15, 2019

Abstract

Methods and apparatuses for version management. Information corresponding to multiple versions of a file is maintained in a database. The information includes one or more versions of the file and change data associated with the one or more versions of the file. In response to a request, a graphical user interface (GUI) is presented that includes a timeline with entries corresponding to one or more versions of the file. The entries have at least a graphical representation of changes made.

First claim

What is claimed is:

1. A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processor, are configurable to cause the one or more processors to:
maintain, with the one or more processors and in a database, information corresponding to multiple versions of a file, wherein the information comprises one or more of the multiple versions of the file and change data associated with the one or more versions of the file and the change data further comprises at least a number of changes and corresponding types of changes for associated versions of the file;
present, with the one or more processors and in response to a request, a graphical user interface (GUI) comprising at least a timeline with entries corresponding to one or more versions of the file, wherein the entries have at least a graphical representation of changes made and wherein the graphical representation comprise graphical characteristics of the entries that vary depending on the number of changes and the types of changes;
provide a mechanism to select an earlier version of the file through the GUI; and
revert to the selected earlier version of the file if no dependencies exist that would result in the selected earlier version having reduced functionality, wherein the version control system operates within an on-demand services environment and monitors dependencies so that reversion to previous versions does not result in a non-functional system.

2. The non-transitory computer-readable medium of claim 1 further comprising instructions that, when executed by the one or more processors, cause the one or more processors to analyze earlier versions of the file to determine whether dependencies exist that would result in the selected earlier version having reduced functionality, wherein the earlier version corresponds to digital data for a tenant in a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application.

3. The non-transitory computer-readable medium of claim 1 wherein the file comprises a source code file.

4. The non-transitory computer-readable medium of claim 3 wherein the source code file corresponds to digital data for a tenant in a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application.

5. The non-transitory computer-readable medium of claim 1 wherein the file comprises an executable code file.

6. The non-transitory computer-readable medium of claim 5 wherein the executable code file corresponds to digital data for a tenant in a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application.

7. The non-transitory computer readable medium of claim 1 wherein the file comprises a word processing file.

8. The non-transitory computer readable medium of claim 1 wherein the request is in response to user input.

9. A method comprising:
maintaining, with one or more processors and in a database, information corresponding to multiple versions of a file, wherein the information comprises one or more of the multiple versions of the file and change data associated with the one or more versions of the file and the change data further comprises at least a number of changes and corresponding types of changes for associated versions of the file;
presenting, with the one or more processors and in response to a request, a graphical user interface (GUI) comprising at least a timeline with entries corresponding to one or more versions of the file, wherein the entries have at least a graphical representation of changes made and wherein the graphical representation comprise graphical characteristics of the entries that vary depending on the number of changes and the types of changes;
providing a mechanism to select an earlier version of the file through the GUI; and
reverting to the selected earlier version of the file if no dependencies exist that would result in the selected earlier version having reduced functionality, wherein the version control system operates within an on-demand services environment and monitors dependencies so that reversion to previous versions does not result in a non-functional system.

10. The method of claim 9 further comprising analyzing earlier versions of the file to determine whether dependencies exist that would result in the selected earlier version having reduced functionality, wherein the earlier version corresponds to digital data for a tenant in a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application.

11. The method of claim 9 wherein the file comprises a source code file.

12. The method of claim 11 wherein the source code file corresponds to digital data for a tenant in a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application.

13. The method of claim 9 wherein the file comprises an executable code file.

14. The method of claim 13 wherein the executable code file corresponds to digital data for a tenant in a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application.

15. The method of claim 9 wherein the file comprises a word processing file.

16. The method of claim 9 wherein the request is in response to user input.

17. A system for managing digital data for a plurality of tenants to software instances, each tenant of the plurality of tenants comprising a group of users who share a common access with a specific set of privileges to a software instance of at least one application, the system to:
maintain, with the one or more processors and in a database, information corresponding to multiple versions of a file, wherein the information comprises one or more of the multiple versions of the file and change data associated with the one or more versions of the file and the change data further comprises at least a number of changes and corresponding types of changes for associated versions of the file;
present, with the one or more processors and in response to a request, a graphical user interface (GUI) comprising at least a timeline with entries corresponding to one or more versions of the file, wherein the entries have at least a graphical representation of changes made and wherein the graphical representation comprise graphical characteristics of the entries that vary depending on the number of changes and the types of changes;
provide a mechanism to select an earlier version of the file through the GUI; and
revert to the selected earlier version of the file if no dependencies exist that would result in the selected earlier version having reduced functionality, wherein the version control system operates within an on-demand services environment and monitors dependencies so that reversion to previous versions does not result in a non-functional system.

Assignees

• Salesforce Com Inc

Inventors

• Schoppe Owen Winne
• Vogt Jr John Fredric
• Toens Simon

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F16/93

  Document management systems · CPC title

• G06F40/197

  Version control (for software G06F8/71) · CPC title

• G06F17/2288

  Physics · mapped topic

• G06F17/30011

  Physics · mapped topic