Hi All, I am writing this to just paraphrase the patch flight process that is in place more or less and I am going to follow.
We have patchwork instance where all patches from mailing list are captured https://patchwork.openembedded.org/project/oe/patches/ I am going to watch this and cherry pick patches from patchwork into master-next branch master-next then will be run through CI loop on my own system as well as on http://jenkins.nas-admin.org/ tasks - oe_world_qemuarm oe_world_qemuarm64 oe_world_qemux86 oe_world_qemux86-64 For layer maintainers Please review and provide your ACK/NACK based upon your own testing and judgement. If you want to rely on the jenkins jobs above thats fine too. If you want to test your bundle separately and send a separate approved patchlist via a pull thats fine too. Usually we do not give explicit ACKs and provide feedback if a patch needs to be changed. It would be good if you start providing ACKs if you think patch is good to signal. If a patch is not ACKED/NACKED and its passing the jenkins builds, I will assume you are OK with the patch for master. Submitters, please watch the patchwork for progress on your submission Hopefully patchwork will reflect the current state more accurately, if its stuck in same state for a long time (1+ weeks ) send the pings to maintainers. you can also check master-next branch if its still there and not dropped then its in queue for merge Since we all have limited resources and time, I would invite all of you to test master-next for machines/distros you are interested in (keep in mind master-next will get rebased) and provide feedback/review so we can include it in decision to accept the patch, any help will be appreciated. If you have suggestions, feel free to share here Thanks -Khem -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
