ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update development workflow description to state of latest discussions

Browse Source
This commit is contained in:
Axel Kohlmeyer
2019-01-31 02:55:11 -05:00
parent 1d6bf1ea7d
commit d2846404bd
1 changed files with 11 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
doc/github-development-workflow.md
View File

@ -50,8 +50,8 @@ This is indicated by who the pull request is assigned to. LAMMPS core
developers can self-assign or they can decide to assign a pull request developers can self-assign or they can decide to assign a pull request
to a different LAMMPS developer. Being assigned to a pull request means, to a different LAMMPS developer. Being assigned to a pull request means,
that this pull request may need some work and the assignee is tasked to that this pull request may need some work and the assignee is tasked to
determine what this might be needed or not, and may either implement the determine whether this might be needed or not, and may either implement
required changes or ask the submitter of the pull request to implement the required changes or ask the submitter of the pull request to implement
them. Even though, all LAMMPS developers may have write access to pull them. Even though, all LAMMPS developers may have write access to pull
requests (if enabled by the submitter, which is the default), only the requests (if enabled by the submitter, which is the default), only the
submitter or the assignee of a pull request may do so. During this submitter or the assignee of a pull request may do so. During this
@ -76,12 +76,15 @@ People can be assigned to review a pull request in two ways:
Reviewers are requested to state their appraisal of the proposed changes Reviewers are requested to state their appraisal of the proposed changes
and either approve or request changes. People may unassign themselves and either approve or request changes. People may unassign themselves
from review, if they feel not competent about the changes proposed. At from review, if they feel not competent about the changes proposed. At
least one review from a LAMMPS developer with write access is required least two approvals from LAMMPS developers with write access are required
before merging in addition to the automated compilation tests. The before merging in addition to the automated compilation tests.
feature, that reviews from code owners are "hard" reviews (i.e. they Merging counts as implicit approval, so does submission of a pull request
must all be approved before merging is allowed), is currently disabled (by a LAMMPS developer). So the person doing the merge may not also submit
and it is in the discretion of the merge maintainer to assess when an approving review. The feature, that reviews from code owners are "hard"
a sufficient degree of approval has been reached. Reviews may be reviews (i.e. they must all be approved before merging is allowed), is
currently disabled and it is in the discretion of the merge maintainer to
assess when a sufficient degree of approval, especially from external
contributors, has been reached in these cases. Reviews may be
(automatically) dismissed, when the reviewed code has been changed, (automatically) dismissed, when the reviewed code has been changed,
and then approval is required a second time. and then approval is required a second time.