Difference: LbSoftUseCases (6 vs. 7)

Revision 72015-11-26 - GerhardRaven

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, develops his/her changes in this branch, and then submits a merge request for this branch. (note: this assumes all development is contained to a single repository)
>
>
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. (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.
 

New Loki functionality needed for a new HLT Line

Contact: Vava
Line: 54 to 55
 Workflow:

persons Alpha, Beta and Gamma start topic branches for each of their developments. Once implemented, they each request a merge request.

Changed:
<
<
X reviews these requests, and decides which one to merge first, lets take Alpha for this. At this point, it is possible that the changes from Beta and Gamma no longer cleanly apply, and X informs Beta and Gamma of this (actually, Beta and Gamma can see this from the gitlab merge request
>
>
Curator X of the 'official' repository reviews these requests, based on eg. feedback from reviewers, and decides which one to merge first, lets take Alpha for this. At this point, it is possible that the changes from Beta and Gamma no longer cleanly apply, and X informs Beta and Gamma of this (actually, Beta and Gamma can see this from their gitlab merge request
 status pages), and asks them to resolve the conflicts, and then processes their requests.

Chosing which reconstruction changes are included in the HLT

Line: 69 to 70
 Priority:

Workflow:

Changed:
<
<
X only merges the merge request from Gamma and Beta, and does not merge Alpha's request....
>
>
X only merges the requests from Gamma and Beta, and decides not to merge Alpha's request....
 

Preparation of HLT Settings

Contact: Vava
Line: 80 to 82
  Priority:
Added:
>
>
Workflow:
  Assuming X merged the requests from Gamma and Beta, there is now a branch with their changes included. Z creates a new branch on top of this branch, and adds the required further changes, which results in yet another merge request. This merge request is then accepted and the
 
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