Toolset.Repository History

Hide minor edits - Show changes to markup - Cancel

May 25, 2005, at 01:28 PM by 62.160.13.213 -
Changed lines 8-9 from:

What does a repository do for Continuous Integration and Collaboration? Collaboration deals with shared ownership and responsibility. Everyone needs to be able to find the work others have done. This way you can collaborate on sources, documents, requirements, etc. Continuous integration deals with creating and recreating builds. A repository must be able to support that.

to:

What does a repository do for Continuous Integration and Collaboration? Collaboration deals with shared ownership and responsibility. Everyone needs to be able to find the work others have done. This way you can collaborate on sources, documents, requirements, etc. Continuous integration deals with creating and recreating builds. A repository must be able to support that..

May 01, 2005, at 11:05 PM by Jettro Coenradie -
Changed lines 8-10 from:

What does a repository do for Continuous Integration and Collaboration? Collaboration deals with shared ownership and responsibility. Everyone needs to be able to find the work others have done. This way you can collaborate on sources, documents, requirements, etc. Continuous integration deals with creating and recreating builds. A repository must be able to support that.

to:

What does a repository do for Continuous Integration and Collaboration? Collaboration deals with shared ownership and responsibility. Everyone needs to be able to find the work others have done. This way you can collaborate on sources, documents, requirements, etc. Continuous integration deals with creating and recreating builds. A repository must be able to support that.

(:showright:)

May 01, 2005, at 10:49 PM by Jettro Coenradie -
Changed lines 6-8 from:
  • Bitkeeper
to:
  • Bitkeeper

What does a repository do for Continuous Integration and Collaboration? Collaboration deals with shared ownership and responsibility. Everyone needs to be able to find the work others have done. This way you can collaborate on sources, documents, requirements, etc. Continuous integration deals with creating and recreating builds. A repository must be able to support that.

May 01, 2005, at 10:31 PM by Jettro Coenradie -
Changed lines 1-6 from:

One of the meanings found on Dictionary.com is : A place where things may be put for safekeeping. Actually this is what software repositories are used for. Keeping track on sources, documents, etc. Enable users to find older versions, find changes and share there work with others.

to:

One of the meanings found on Dictionary.com is : A place where things may be put for safekeeping. Actually this is what software repositories are used for. Keeping track on sources, documents, etc. Enable users to find older versions, find changes and share there work with others. The term used very often for a software repository is Source Control Management system. A few examples that are used extensively are:

  • CVS
  • Subversion
  • IBM Rational Clearcase
  • Visual source safe
  • Bitkeeper
May 01, 2005, at 10:20 PM by Jettro Coenradie -
Changed line 1 from:

Subversion

to:

One of the meanings found on Dictionary.com is : A place where things may be put for safekeeping. Actually this is what software repositories are used for. Keeping track on sources, documents, etc. Enable users to find older versions, find changes and share there work with others.

April 24, 2005, at 07:48 PM by Jettro Coenradie -
Changed line 1 from:

Discuss repository tools

to:

Subversion

April 19, 2005, at 11:57 PM by Jettro Coenradie -
Changed line 1 from:

Discuss repository

to:

Discuss repository tools

April 19, 2005, at 11:57 PM by Jettro Coenradie -
Added line 1:

Discuss repository


Page last modified May 25, 2005, at 01:28 PM