We need to migrate and document trees from Legacy system to Maestro.
I suggest to do it in following steps:
Figure out contact person of tree
Confirm contact is correct or update contact, request if they want to be migrated to Maestro system with following short questions:
Record answers and submit to kernelci-project/maintainers/trees.yaml
Questions:
Do you want to participate on early stages of development? E.g. participate in discussions on kernel options, tests we are enabling, reporting format, etc., so we keep you up to date with short summaries and you can provide feedback.
What kind of reports do you want to receive? E.g. complete build report with links to logs on each checkout, short build summary, only automatically detected regressions, only human verified regressions(we have limited capacity on this and might miss some regressions), etc. Feel free to suggest your own format.
What compilers + architectures + configuration do you want to be tested? Is default set OK for you?
Do you want to test your tree on real hardware in labs? Do you have any tree specific tests you want to run and you can provide assistance with maintenance of this tests?
As follow up we need to create issue template for kernelci-project for new maintainers, with semi-automated submission of tree to configuration files.
# Format of file is also documented at top of file in comments
# This file is used to store information about trees that are being tested by kernelci
# It is used to store information about the tree, the contact person, the mailing list, the build configurations, and the type of report that is desired
# Mail addresses are obfuscated to prevent spam with ROT13 (Rot13 / Caesar)
# build_configs is kernel configurations important for maintainer, special types are: default (default set of configurations kernelci builds)
# arch/compiler/defconfig+fragments
# For example: x86_64/gcc-12/x86_64_defconfig
# report_type is the type of report that is desired, with the following options:
# full: full build report with links to logs on each checkout
# short: short build summary
# regressions: only automatically detected regressions
# human: only human verified regressions(we have limited capacity on this and might miss some regressions)
treename:
development_participation: true
contact: obfuscated contact email
contact_name: contact name
maillist: obfuscated mailing list email
build_configs:
- arch/compiler/defconfig+fragments
- x86_64/gcc-12/x86_64_defconfig
- mips/gcc-12/malta_defconfig
report_type: full
report_emails:
- obfuscated email1
- optional obfuscated email2
- ...
We need to migrate and document trees from Legacy system to Maestro.
I suggest to do it in following steps:
Questions:
As follow up we need to create issue template for kernelci-project for new maintainers, with semi-automated submission of tree to configuration files.
List of trees to migrate:
trees.yaml format is following: