[dpdk-dev] [PATCH] doc: add details on requirements for patch ack and merge

Thomas Monjalon thomas.monjalon at 6wind.com
Tue Feb 21 15:12:32 CET 2017


2017-02-21 12:02, Bruce Richardson:
> +#. Once a patch has been acked by the relevant maintainer, reviewers may still comment on it for a further
> +   two weeks. After that time, the patch should be merged into the relevent git tree for the next release.
> +   Additional notes and restrictions:
> +
> +   * patches should be acked by a maintainer at least two days before the release merge
> +     deadline, in order to make that release.
> +   * for patches acked with less than two weeks to go to the merge deadline, all additional
> +     comments should be made no later than two days before the merge deadline.

Do we need a drawing to illustrate the deadlines? :)

> +   * after the appropriate time for additional feedback has passed, if the patch has not yet
> +     been merged to the relevant tree by the committer, it should be treated as though it had,
> +     in that any additional changes needed to it must be addressed by a follow-on patch, rather
> +     than rework of the original.
> +   * trivial patches may be merged sooner than described above at the tree committer's
> +     discretion.

Is it a trivial patch or should I wait 2 weeks before merging this one?

Acked-by: Thomas Monjalon <thomas.monjalon at 6wind.com>



More information about the dev mailing list