Difference: LbSoftUseCases (8 vs. 9)

Revision 92015-11-27 - TimHead

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Development Use Cases

Line: 21 to 21
  Priority: High
Changed:
<
<
Workflow: Developer creates a new 'topic' branch of the relevant repository, develops his/her changes in this branch, and then submits a merge request for this branch.
>
>
Workflow: Developer creates a fork of the HLT repo, in that fork they create a new 'topic' branch of the relevant repository, develops his/her changes in this branch, and then submits a merge request from their fork to the main repository.
 (note: this assumes all development is contained to a single repository). The curator(s) of the 'official' repository decides whether or not, possibly after feedback from a code review, to accept the merge request.
Line: 36 to 36
  Workflow:
Changed:
<
<
Vanya starts a new topic branch, and implements the requested functionality, and then creates a merge request for this branch.
>
>
Vanya forks the LoKi repository, and in the fork starts a new topic branch, and implements the requested functionality, and then creates a merge request from his repository to the main repository.
 Two different cases can happen: 1) the development is fully contained within the 'HLT' project repository, in which case no further action is required. 1) the changes pertain to other projects. This needs to be further worked out, but something on top of git subtree is presumably appropriate -- see eg. https://developer.atlassian.com/blog/2015/05/the-power-of-git-subtree/ or http://tdd.github.io/git-stree/ -- one can import 'part' of another git repo inside the current repo.
Added:
>
>
Discussion: I think the general recommendation is to avoid using subtree, submodule and other sub* tools with git (http://blogs.atlassian.com/2014/04/git-project-dependencies/). The real solution is to have a package manager that deals with dependencies between projects/repositories. What we need is an `environment` which contains one or more repositories. In this particular case you would clone the two repositories containing the changes you are interested in testing together (in this case the forks of the HLT and LoKi repositories which contain the proposed changes) and build them. Together they form an `environment`, in which you run what ever things you need to run. --Tim
 

Test of the newly developed reconstruction code feects on HLT line under development

Contact: Vava

Line: 73 to 75
  X only merges the requests from Gamma and Beta, and decides not to merge Alpha's request....
Added:
>
>
Discussion: is this meant to chronologically follow the previous scenario or is an alternative to it? --Tim
 

Preparation of HLT Settings

Contact: Vava
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback