Logistic. 3.1 Candidate releases management The delivery of the D-Net 1.0 software release is to be preceded by two pre-releases (one alpha and one beta), a first release candidate (rc1) and optionally a second release candidate. The source code and binaries of each release (including pre-releases) shall be correctly packaged and stored on the official release package repository, but only the release candidate and D-Net 1.0 release code shall be available for public download from the repository. Once an pre-release is issued, the current public visible Testbed infrastructure (known as production infrastructure) will be upgraded with the respective pre-release code base. The release candidate code base instead will not be applied over the current public production infrastructure, but a new set of machines will be dedicated for it's deployment. The new production deployment will start with the release candidate software release and will be subsequently updated until it becomes the new public production infrastructure running the final D-Net 1.0 release code base. Here is a more detailed view of each release step: • The alpha release is to be issued at the end of March 2008. The release will contain the latest stable version of the services, namely that shown for the review. Some of the functionalities may be missing, but the resulting infrastructure will be stable for demos and Information Space maintenance. Note: alpha v1 coincides with the final production of the DRIVER Testbed, developed by the DRIVER Project. • The beta release is to be issued at the end of April 2008. The release will contain the latest stable version of the services, independently from their current status of development, available for all partners to develop in stable environments. The idea is to start deploying the services and initiate testing with relevant and significant data. If some component is stable enough it may be used to update the current production infrastructure. • The first release candidate 1 (rc1) is to be issued the 15th of May 2008. The release will contain the last stable version of the Services, for those Services that reached stability, deployed on new production machines according to a specific plan and available for download and installation to the public. Except for unexpected blocking emergencies, such Services should only be maintained up and running. In such context we expect to harvest, store and migrate the real Information Space data. This release will become ful...
Logistic. 41.1 PARTNER shall provide all logistic necessity from the origin of the Goods To Be Transferred or other Project material to Location/Project Site, including all costs, such as freight forwarding and transit, docking fee, storage, insurance, expenses and levies. Further, PARTNER shall state service costs related to all equipment (including survey, design, planning, permit, right to cross, service related to land obtainment, installation, integration, project management, insurance until the assignment of right, test and acceptance test, in accordance with Article 10.2, test and acceptance test, and all material and related expenses) for the imported and local goods.
Logistic. ▪ Transport costs of technical personnel ▪ Equipment up to the parking space next to the venue Organiser obligations Staff
