Common use of DOCUMENT AND SOURCE CODE MANAGEMENT REPOSITORY Clause in Contracts

DOCUMENT AND SOURCE CODE MANAGEMENT REPOSITORY. The Supplier shall, at the end of each Sprint (unless otherwise agreed with the Customer) upload to the Repository the following items: all developed live code for the current software release, daily software builds, test scripts, technical libraries, archive libraries, source code, object code, automated build configurations, dependencies, environments, schema, Sprint and Release details, current development orders, change control notices, Product Backlog/ice box) and any other project specific documentation or items as may be requested by the Customer.

DOCUMENT AND SOURCE CODE MANAGEMENT REPOSITORY. 18.1 The Supplier shall, at the end of each Sprint (unless otherwise agreed with the Customer) upload to the Repository the following items: all developed live code for the current software release, daily software builds, test scripts, technical libraries, archive libraries, source code, object code, automated build configurations, dependencies, environments, schema, Sprint and Release details, current development orders, change control notices, Product Backlog/ice box) and any other project specific documentation or items as may be requested by the Customer.

DOCUMENT AND SOURCE CODE MANAGEMENT REPOSITORY. ‌ 18.1 The Supplier shall, at the end of each Sprint (unless otherwise agreed with the Customer) upload to the Repository the following items: all developed live code for the current software release, daily software builds, test scripts, technical libraries, archive libraries, source code, object code, automated build configurations, dependencies, environments, schema, Sprint and Release details, current development orders, change control notices, Product Backlog/ice box) and any other project specific documentation or items as may be requested by the Customer.

DOCUMENT AND SOURCE CODE MANAGEMENT REPOSITORY. 18.1 The Supplier shall, at the end of each Sprint (unless otherwise agreed with the Customer) upload to the Repository the following items: all developed live code for the current software release, daily software builds, test scripts, technical libraries, archive libraries, source code, object code, automated build configurations, dependencies, environments, schema, Sprint and Release details, current development orders, change control notices, Product Backlog/ice box) and any other project specific documentation or items as may be requested by the CustomerCustomer .