From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4E3CB43421; Fri, 1 Dec 2023 18:24:26 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DD54E40298; Fri, 1 Dec 2023 18:24:25 +0100 (CET) Received: from mail-oa1-f52.google.com (mail-oa1-f52.google.com [209.85.160.52]) by mails.dpdk.org (Postfix) with ESMTP id 32EDE4025F for ; Fri, 1 Dec 2023 18:24:24 +0100 (CET) Received: by mail-oa1-f52.google.com with SMTP id 586e51a60fabf-1efb9571b13so419896fac.2 for ; Fri, 01 Dec 2023 09:24:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1701451463; x=1702056263; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JyegifbQ4U02XdbIM89ECxAzH0t1B+9PEJ2OEN7awjc=; b=BcXNHKcb+hn8B5P8fyvmQIlVDDDynn5RQAmXePCQ73+/ELYONbAWB8lfGS9Hci5Hw2 BDTVOehDRFJA3oNIV8D+RZ94LDmdbbWtpTQpPlVg6YXk6j1yPxcsbnC9Pf8i/nbCD8Bc FkomW1OK4+xScpH3DZW8YXyGvICeU8d9M5/7s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701451463; x=1702056263; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JyegifbQ4U02XdbIM89ECxAzH0t1B+9PEJ2OEN7awjc=; b=wD9vFI792M7Gsw+T9CibnK+CKUG/6vZisXC8Fv/xXuTUNigfu7X6Z2Iw1tKVAXpLdh jh/N1GUE8EDjB9A3ixxfkY2JabnHhnqqw7GUTzrF2PWBIa3xspHKE9H8wnSPgtru4er+ 7q8FMGboQ+Uk5+jJEen/pzFKPGaLWbzG+aqkcBDuuVmVoZme/9mwqoUyPdsHytxX6NtE nU75qqPYVdfGm2H8pgZ7lMP3aMeImJOAhRtSa7HTiyoCPnOebiDNsGzti7rY96HA3EbO gDJGG3ViPPJJ1YSMe5pSNmPiQNCyFyo2/SLSZL/rOvZYy0hV0O6OHzq1zbpiIKjvyM0/ 3uNw== X-Gm-Message-State: AOJu0YxUB4OPwAvLod7cvRySCtt0DMzRVcoi/SfCgsx02RnWy5lZbaS7 l6/VmresDaWDvb7sQPGpaxvJi6bXE8qTPCS9nerOyQ== X-Google-Smtp-Source: AGHT+IGAFU5uD1OcKvs7Z2HXjyGqURA2CDwAKs0yTvYGDUo9OKh3VuZvYnjUiqr5RG4f4S+rsBUze1NR/55PBzO0oR0= X-Received: by 2002:a05:6870:40c3:b0:1fa:2d82:b89a with SMTP id l3-20020a05687040c300b001fa2d82b89amr24937691oal.3.1701451463336; Fri, 01 Dec 2023 09:24:23 -0800 (PST) MIME-Version: 1.0 References: <20231129161858.997576-1-david.marchand@redhat.com> <7128906.ZaRXLXkqSa@thomas> In-Reply-To: From: Patrick Robb Date: Fri, 1 Dec 2023 12:24:12 -0500 Message-ID: Subject: Re: [PATCH] version: 24.03-rc0 To: Ferruh Yigit Cc: Bruce Richardson , Thomas Monjalon , David Marchand , dev@dpdk.org, Aaron Conole , Michael Santana , Andrew Rybchenko , Ajit Khaparde , Qi Zhang , Jerin Jacob Kollanukkaran , Raslan Darawsheh , Maxime Coquelin , Akhil Goyal Content-Type: multipart/alternative; boundary="0000000000001342e6060b760ad9" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000001342e6060b760ad9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Dec 1, 2023 at 11:36=E2=80=AFAM Ferruh Yigit = wrote: > On 12/1/2023 2:30 PM, Bruce Richardson wrote: > > On Fri, Dec 01, 2023 at 11:33:25AM +0000, Ferruh Yigit wrote: > >> On 12/1/2023 11:13 AM, Bruce Richardson wrote: > >>> On Fri, Dec 01, 2023 at 09:04:10AM +0100, Thomas Monjalon wrote: > >>>> 30/11/2023 19:33, Patrick Robb: > >>>>> On Thu, Nov 30, 2023 at 4:24=E2=80=AFAM David Marchand < > david.marchand@redhat.com> > >>>>> wrote: > >>>>> > >>>>>> What it means: > >>>>>> - for the https://dpdk.org/git/dpdk repository, all the branches > and > >>>>>> tags are mirrored to https://github.com/DPDK/dpdk as it was done s= o > >>>>>> far, > >>>>>> - for the https://git.dpdk.org/next/dpdk-next-* repositories, only > >>>>>> branches named "main", "staging" or "for-*" are mirrored to > >>>>>> https://github.com/DPDK/dpdk with a prefix. > >>>>> > >>>>> Thank you David for clearing some of this up on the CI testing > meeting. I > >>>>> think the final loose end was you were wondering which branches > within the > >>>>> next-* repos we were running from. I'll paste that below: > >>>>> > >>>>> dpdk-next-crypto: for-main > >>>>> dpdk-next-eventdev: for-main > >>>>> dpdk-next-net: main > >>>>> dpdk-next-net-brcm: main > >>>>> dpdk-next-net-intel: main > >>>>> dpdk-next-net-mlx: main > >>>>> dpdk-next-net-mrvl: for-next-net > >>>>> dpdk-next-virtio: main > >>>>> dpdk-next-baseband: for-main > >>>> > >>>> We should test patches on top of the branch which is validated > >>>> by the tree maintainer and ready to pull. > >>>> This is the default branch (HEAD) of its repository on dpdk.org. > >>>> This is the list of equivalent GitHub branches to use for testing: > >>>> > >>>> main > >>>> next-baseband-for-main > >>>> next-crypto-for-main > >>>> next-eventdev-for-main > >>>> next-net-for-main-repo > >>> > >>> The (slight) inconsistency here is curious. Is there a reason why thi= s > >>> branch has "repo" on the end and none of the others don't? > >>> > >> > >> No specific reason, it started like that in the past. If the consensus > >> is to go with 'for-main', I can update it. > >> > > In all likelihood it's not a big deal. > > > > I'm just thinking that for any future automation or tracking, having a > very > > consistent naming would be best. For example, in the one-liner I posted > for > > generating the graph showing the inter-tree flow, I needed a special > regex > > to strip off the "-repo", so that we didn't have a separate target call= ed > > "main-repo" and another called "main". > > > > Agree on above, created 'for-main' branch and will use it now. > > But I need help from Thomas/David to delete remote 'for-main-repo' branch= . > > 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. 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). Thanks! --0000000000001342e6060b760ad9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Fri, Dec 1, 2023 at 11:36=E2=80=AFAM F= erruh Yigit <ferruh.yigit@amd.co= m> wrote:
On 12/1/2023 2:30 PM, Bruce Richardson wrote:
> On Fri, Dec 01, 2023 at 11:33:25AM +0000, Ferruh Yigit wrote:
>> On 12/1/2023 11:13 AM, Bruce Richardson wrote:
>>> On Fri, Dec 01, 2023 at 09:04:10AM +0100, Thomas Monjalon wrot= e:
>>>> 30/11/2023 19:33, Patrick Robb:
>>>>> On Thu, Nov 30, 2023 at 4:24=E2=80=AFAM David Marchand= <david.m= archand@redhat.com>
>>>>> wrote:
>>>>>
>>>>>> What it means:
>>>>>> - for the https://dpdk.org/git/dpdk repository= , all the branches and
>>>>>> tags are mirrored to https://github.com/DPDK/dp= dk as it was done so
>>>>>> far,
>>>>>> - for the https://git.dpdk.org/next/dp= dk-next-* repositories, only
>>>>>> branches named "main", "staging&quo= t; or "for-*" are mirrored to
>>>>>> https://github.com/DPDK/dpdk with a prefix.=
>>>>>
>>>>> Thank you David for clearing some of this up on the CI= testing meeting. I
>>>>> think the final loose end was you were wondering which= branches within the
>>>>> next-* repos we were running from. I'll paste that= below:
>>>>>
>>>>> dpdk-next-crypto: for-main
>>>>> dpdk-next-eventdev: for-main
>>>>> dpdk-next-net: main
>>>>> dpdk-next-net-brcm: main
>>>>> dpdk-next-net-intel: main
>>>>> dpdk-next-net-mlx: main
>>>>> dpdk-next-net-mrvl: for-next-net
>>>>> dpdk-next-virtio: main
>>>>> dpdk-next-baseband: for-main
>>>>
>>>> We should test patches on top of the branch which is valid= ated
>>>> by the tree maintainer and ready to pull.
>>>> This is the default branch (HEAD) of its repository on dpdk.org.=
>>>> This is the list of equivalent GitHub branches to use for = testing:
>>>>
>>>>=C2=A0 =C2=A0 main
>>>>=C2=A0 =C2=A0 next-baseband-for-main
>>>>=C2=A0 =C2=A0 next-crypto-for-main
>>>>=C2=A0 =C2=A0 next-eventdev-for-main
>>>>=C2=A0 =C2=A0 next-net-for-main-repo
>>>
>>> The (slight) inconsistency here is curious. Is there a reason = why this
>>> branch has "repo" on the end and none of the others = don't?
>>>
>>
>> No specific reason, it started like that in the past. If the conse= nsus
>> is to go with 'for-main', I can update it.
>>
> In all likelihood it's not a big deal.
>
> I'm just thinking that for any future automation or tracking, havi= ng a very
> consistent naming would be best. For example, in the one-liner I poste= d for
> generating the graph showing the inter-tree flow, I needed a special r= egex
> to strip off the "-repo", so that we didn't have a separ= ate target called
> "main-repo" and another called "main".
>

Agree on above, created 'for-main' branch and will use it now.

But I need help from Thomas/David to delete remote 'for-main-repo' = branch.

Great. So for CI testing, we will use dpdk-*-for-main wh= en 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= .=C2=A0

For staging branches, Based on TB voting I did a= dd a work item to the 2024 lab SOW for "on-push" staging branch t= esting, which we will do via these GitHub branches (so like, next-virtio-st= aging).=C2=A0

Thanks!
--0000000000001342e6060b760ad9--