Re: [PATCH] version: 24.03-rc0

[Thomas Monjalon <thomas@monjalon.net>]

30/11/2023 19:33, Patrick Robb:
> On Thu, Nov 30, 2023 at 4:24 AM 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 so
> > 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
	next-net-brcm-for-next-net
	next-net-intel-for-next-net
	next-net-mlx-for-next-net
	next-net-mrvl-for-main
	next-virtio-for-next-net