On Wed, Jul 13, 2022 at 07:46:28PM +0200, Heinrich Schuchardt wrote:
On 7/11/22 19:14, Tom Rini wrote:
The "Workflow of a Custodian" section on the wiki had not been changed in quite some time to reflect how the process has been functioning for some time. First, update some links to point to modern and current sources of information.
Second, and more overarching, reword much of the section. This expands on the expectations of both custodians and developers when it comes to rebasing patches. Rework the final points to be clearer that Custodians are expected to do their best to test the changes and ask for help when needed, as well as that pull requests are expected in a timely manner.
Cc: Claudius Heine ch@denx.de Cc: Martin Bonner martingreybeard@gmail.com Cc: Heinrich Schuchardt xypron.glpk@gmx.de Signed-off-by: Tom Rini trini@konsulko.com
Changes in v2:
- New patch
[snip]
-#. Once tests are passed, some agreed time limit expires, the custodian
- requests that the changes in their public git repository be merged into the
- main tree. If necessary, the custodian may have to adapt their changes to
- allow for a clean merge.
- Todo: define a reasonable time limit. 3 weeks?
+#. Custodians are expected to submit a timely pull request of their git
- repository to the main repository. It is strongly encouraged that a CI run
- have been complete prior to submission, but not required.
A run is singular.
Oops, thanks.