Search results

From Gcube Wiki
Jump to: navigation, search

Page title matches

Page text matches

  • ...stallation, are of the same release with the target infrastructure and its release)''' * Download the gCube gHN of the desired release from the ETICS build report (https://grids16.eng.it/BuildReport/browse/Rece
    34 KB (5,521 words) - 11:55, 20 January 2014
  • Other development activities results from defects discovered after the release of the artifacts (e.g. known bugs). These are captured by two specific live Other development activities results from defects discovered after the release of the artifacts (e.g. known bugs). These are captured by two specific live
    17 KB (2,354 words) - 20:01, 6 July 2016
  • //Close the reader to release and dispose any resources in boith reader and writer sides //Close the reader to release and dispose any resources in both reader and writer sides
    47 KB (6,583 words) - 19:02, 11 December 2013
  • gCube as chosen to move to Liferay Portal from its 1.9 release. ...rforming this operation (plus some others) is available starting from this release. See [https://wiki.gcube-system.org/gcube/Portal_Context Portal Context] fo
    16 KB (2,211 words) - 13:00, 18 January 2017
  • :* ''Ready To Release'', used when the activities described in a ticket are completed and the res ...e-system.org/index.php?option=com_distribution&view=distribution&Itemid=23&release=HEAD '''Development Version'''] (Login is required) || align="center"|[http
    10 KB (1,433 words) - 16:41, 3 November 2011
  • * A major release closure. In this case the responsible for initiating the procedure is the [
    40 KB (4,752 words) - 19:05, 6 July 2016
  • ...adoc in the [https://www.gcube-system.org/software-releases gCube Software Release page]
    12 KB (1,556 words) - 15:06, 18 May 2017
  • = Release org.gcube.4-0-0 full changelog = Second Release
    9 KB (805 words) - 15:38, 28 July 2016
  • ...ng [[Major/Minor Release Cycle procedure|Release Cycles]] or [[Maintenance Release Cycle procedure|Maintenance Cycles]], candidate configuration is built to s ...a [[Major/Minor Release Cycle procedure|Release Cycle]] or a [[Maintenance Release Cycle procedure|Maintenance Cycle]] start, components to be included in the
    8 KB (1,068 words) - 00:58, 4 November 2015
  • * '''/branches''': contains branches created during release cycles to release and integrate candidate versions of gCube components ...a complex change without interfering with the stability of /trunk. Unlike release branches (which may need to be supported forever), feature branches are bor
    6 KB (860 words) - 11:31, 13 January 2012
  • ...lidation, and distribution of the system for developers, software testers, release managers, and for any other actor involved in the development of the system ...he timing of the different actors to achieve the desired result. Section [[Release Procedures]] provides a detailed description of each procedure by listing a
    3 KB (349 words) - 06:00, 3 May 2019
  • The tools that take part to the integration of software during a release process are very well integrated each other in order to guarantee an high l ...all gCube software deployable in a given gCube instance. At the end of the release process, the profile of all components released are pushed in the D4Science
    2 KB (345 words) - 12:24, 8 November 2016
  • ...s is made up of '''Milestones'''. The target of a Milestone is a new gCube release. Inside each Milestone, the work is mainly organized into '''Sprints'''. A ...o defects found in candidate releases of the gCube System, and (iv) manage release procedures (e.g. start of releases, subsystem configurations attachment etc
    4 KB (676 words) - 10:20, 22 December 2016
  • ...section we define a set of roles and their duties and responsibilities in release activities. When possible, name and contact of persons playing the differen == Release Roles in a nutshell ==
    1 KB (201 words) - 09:25, 22 December 2016
  • The Release Manager is responsible for the management of the gCube Release and Maintenance Cycles. The main tasks are: * publishes the release plan with deadlines for opening/closing the releases
    1 KB (134 words) - 14:49, 28 September 2015
  • * releases new Subsystem Configurations (see [[Major/Minor Release Cycle procedure##Delivering_Subsystems_.28SMan.29|Delivering Subsystem sect * notifies [[Role Release Manager|Release Manager]] about Subsystem Configurations releases
    8 KB (747 words) - 11:50, 26 March 2018
  • ...ementation of components (including coding, prototyping, early testing and release to the integration stage). Their main tasks are: * [[Major/Minor Release Cycle procedure|Major/Minor Release Cycle]]
    1 KB (157 words) - 18:12, 2 November 2015
  • * [[Major/Minor Release Cycle procedure|Major/Minor Release Cycle]] * [[Maintenance Release Cycle procedure|Maintenance Release Cycle]]
    7 KB (612 words) - 11:58, 26 March 2018
  • ...ntegration and Release/Maintenance cycles of gCube software. It is used by Release Managers, Subsystem Managers and Developers to quickly identify integration
    4 KB (598 words) - 16:19, 10 December 2016
  • ...uild Servers are used to run automatic builds of development and candidate release configurations of gCube, as well as to run un-scheduled manual builds. ...run builds of different configurations simultaneously (very useful during release cycles).
    6 KB (914 words) - 11:09, 11 January 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)