<div dir="ltr"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 1, 2023 at 11:36 AM Ferruh Yigit <<a href="mailto:ferruh.yigit@amd.com">ferruh.yigit@amd.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/1/2023 2:30 PM, Bruce Richardson wrote:<br>
> On Fri, Dec 01, 2023 at 11:33:25AM +0000, Ferruh Yigit wrote:<br>
>> On 12/1/2023 11:13 AM, Bruce Richardson wrote:<br>
>>> On Fri, Dec 01, 2023 at 09:04:10AM +0100, Thomas Monjalon wrote:<br>
>>>> 30/11/2023 19:33, Patrick Robb:<br>
>>>>> On Thu, Nov 30, 2023 at 4:24 AM David Marchand <<a href="mailto:david.marchand@redhat.com" target="_blank">david.marchand@redhat.com</a>><br>
>>>>> wrote:<br>
>>>>><br>
>>>>>> What it means:<br>
>>>>>> - for the <a href="https://dpdk.org/git/dpdk" rel="noreferrer" target="_blank">https://dpdk.org/git/dpdk</a> repository, all the branches and<br>
>>>>>> tags are mirrored to <a href="https://github.com/DPDK/dpdk" rel="noreferrer" target="_blank">https://github.com/DPDK/dpdk</a> as it was done so<br>
>>>>>> far,<br>
>>>>>> - for the <a href="https://git.dpdk.org/next/dpdk-next-*" rel="noreferrer" target="_blank">https://git.dpdk.org/next/dpdk-next-*</a> repositories, only<br>
>>>>>> branches named "main", "staging" or "for-*" are mirrored to<br>
>>>>>> <a href="https://github.com/DPDK/dpdk" rel="noreferrer" target="_blank">https://github.com/DPDK/dpdk</a> with a prefix.<br>
>>>>><br>
>>>>> Thank you David for clearing some of this up on the CI testing meeting. I<br>
>>>>> think the final loose end was you were wondering which branches within the<br>
>>>>> next-* repos we were running from. I'll paste that below:<br>
>>>>><br>
>>>>> dpdk-next-crypto: for-main<br>
>>>>> dpdk-next-eventdev: for-main<br>
>>>>> dpdk-next-net: main<br>
>>>>> dpdk-next-net-brcm: main<br>
>>>>> dpdk-next-net-intel: main<br>
>>>>> dpdk-next-net-mlx: main<br>
>>>>> dpdk-next-net-mrvl: for-next-net<br>
>>>>> dpdk-next-virtio: main<br>
>>>>> dpdk-next-baseband: for-main<br>
>>>><br>
>>>> We should test patches on top of the branch which is validated<br>
>>>> by the tree maintainer and ready to pull.<br>
>>>> This is the default branch (HEAD) of its repository on <a href="http://dpdk.org" rel="noreferrer" target="_blank">dpdk.org</a>.<br>
>>>> This is the list of equivalent GitHub branches to use for testing:<br>
>>>><br>
>>>> main<br>
>>>> next-baseband-for-main<br>
>>>> next-crypto-for-main<br>
>>>> next-eventdev-for-main<br>
>>>> next-net-for-main-repo<br>
>>><br>
>>> The (slight) inconsistency here is curious. Is there a reason why this<br>
>>> branch has "repo" on the end and none of the others don't?<br>
>>><br>
>><br>
>> No specific reason, it started like that in the past. If the consensus<br>
>> is to go with 'for-main', I can update it.<br>
>><br>
> In all likelihood it's not a big deal.<br>
> <br>
> I'm just thinking that for any future automation or tracking, having a very<br>
> consistent naming would be best. For example, in the one-liner I posted for<br>
> generating the graph showing the inter-tree flow, I needed a special regex<br>
> to strip off the "-repo", so that we didn't have a separate target called<br>
> "main-repo" and another called "main".<br>
> <br>
<br>
Agree on above, created 'for-main' branch and will use it now.<br>
<br>
But I need help from Thomas/David to delete remote 'for-main-repo' branch.<br>
<br>
</blockquote></div>Great. So for CI testing, we will use dpdk-*-for-main when possible. next-virtio only has for-next-net and staging, so we will use for-next-net, unless we want to rename that one too to have a true standard. <div><br></div><div>For staging branches, Based on TB voting I did add a work item to the 2024 lab SOW for "on-push" staging branch testing, which we will do via these GitHub branches (so like, next-virtio-staging). </div><div><br></div><div>Thanks!</div></div>