Version control system

1. A version control system, comprising:

at least one server computer;

at least one storage device having a database that stores a plurality of tasks, each task having one or more versions, each version of a given task having files that are associated thereto, wherein each task having associated metadata, wherein the metadata includes a user assignment field, that enables assignment of the task to a user;

a server process, executed by said at least one server computer, that manages versioning of the tasks;

wherein responsive to a request to check-out a first version of the given task, the server process retrieves and serves files associated to the first version of the given task;

wherein responsive to a request to check-in the previously checked-out first version of the given task, the server process generates a second version of the given task, and receives and stores files in association with the second version of the given task; and

wherein responsive to the request to check-in the previously checked-out first version of the given task, the server process receives updates to the metadata associated to the given task, and stores the updates in association with the second version of the given task.

2. The version control system of claim 1 , wherein the files stored in association with the second version of the given task include modified ones of the files associated to the first version of the given task.

3. The version control system of claim 1 , wherein the files stored in association with the second version of the given task include one or more new files that are not associated to the first version of the given task.

4. The version control system of claim 1 , wherein the metadata associated to the given task includes one or more editable attributes for the task, each editable attribute having a name, type, and value.

5. The version control system of claim 1 , wherein the requests to check-out and check-in are received over a network from a client user interface executed by a client device.

6. The version control system of claim 5 , wherein the retrieval and serving of the files associated to the first version of the given task copies said files to the client device.

7. The version control system of claim 5 , wherein the files stored in association with the second version of the given task are received from the client device.

8. The version control system of claim 5 , wherein the request to check-out is processed through the client user interface without individually selecting the files associated to the first version of the task.

9. The version control system of claim 1 , wherein the associated metadata for each task further includes scheduling information for the task including one or more of a start date, a due date, and a completion date.

10. A non-transitory computer readable medium having program instructions embodied thereon, that, when executed by at least one server computer, cause said at least one server computer to implement a version control system, said version control system comprising:

a database that stores a plurality of tasks, each task having one or more versions, each version of a given task having files that are associated thereto, wherein each task having associated metadata, wherein the metadata includes a user assignment field, that enables assignment of the task to a user;

a server process that manages versioning of the tasks;

wherein responsive to a request to check-out a first version of the given task, the server process retrieves and serves files associated to the first version of the given task;

wherein responsive to a request to check-in the previously checked-out first version of the given task, the server process generates a second version of the given task, and receives and stores files in association with the second version of the given task; and

wherein responsive to the request to check-in the previously checked-out first version of the given task, the server process receives updates to the metadata associated to the given task, and stores the updates in association with the second version of the given task.

11. The non-transitory computer readable medium of claim 10 , wherein the files stored in association with the second version of the given task include modified ones of the files associated to the first version of the given task.

12. The non-transitory computer readable medium of claim 10 , wherein the files stored in association with the second version of the given task include one or more new files that are not associated to the first version of the given task.

13. The non-transitory computer readable medium of claim 10 , wherein the metadata associated to the given task includes one or more editable attributes for the task, each editable attribute having a name, type, and value.

14. The non-transitory computer readable medium of claim 10 , wherein the requests to check-out and check-in are received over a network from a client user interface executed by a client device.

15. The non-transitory computer readable medium of claim 14 , wherein the retrieval and serving of the files associated to the first version of the given task copies said files to the client device.

16. The non-transitory computer readable medium of claim 14 , wherein the files stored in association with the second version of the given task are received from the client device.

17. The non-transitory computer readable medium of claim 14 , wherein the request to check-out is processed through the client user interface without individually selecting the files associated to the first version of the task.

18. The non-transitory computer readable medium of claim 10 , wherein the associated metadata for each task further includes scheduling information for the task including one or more of a start date, a due date, and a completion date.