[Buildroot] [PATCH v1 2/3] configs/zynq_zed_defconfig: bump to xilinx-v2023.2

[Peter Korsgaard]

>>>>> "Michal" == Michal Simek <michal.simek at amd.com> writes:

Hi,

>>> commit 496752408d031f93159fcf1aba2831c807a389a3 (tag:
 >>> xlnx_rebase_v6.1_LTS_2023.1_merge_6.1.50,
 >>> xlnx/xlnx_rebase_v6.1_LTS_2023.1_update)
 >>> Merge: 0f7f048016e0 a2943d2d9a00
 >>> Author: Radhey Shyam Pandey <radhey.shyam.pandey at amd.com>
 >>> Date:   Wed Sep 20 17:50:18 2023 +0530
 >> 
 >>> Merge tag 'v6.1.50' into xlnx_rebase_v6.1_LTS_2023.1_update
 >> 
 >>> - U-Boot v2023.01 with additional bug fixes
 >> I noticed that and I actually have the same question.
 >> @Simek, Michal, perhaps you can shed some light on this?
 >> In addition to Peter's question, should we be bumping the Linux
 >> kernel release tag we use with buildroot each time we merge with
 >> another set of 10 upstream patches?

 > It is because our internal deadlines and associated work in connection
 > to our releases.
 > When .1 version is tagged we are merging every 10th LTS version on the
 > top of xilinx 2023.1 tag.

 > On .2 version we continue to do new development and we reached the
 > time where there shouldn't be major changes merged to that
 > branch. That's why .2 version stopped at .30 for running all
 > regressions and .1 can move on .40/.50(coming soon).

Coming soon? .1.50 was tagged 4 weeks ago (see above).


 > I see that xlnx_rebase_v6.1_LTS_2023.2 has been created. That means
 > that next step is going to be that we will do merges for both branches
 > to 6.1.60.
 > At that time both branches will be using the same LTS release.

 > And we should be doing merges to both branches till ~ April 2024.

Ok, thanks! So +/- until the (presumably 6.6 based?) 2024.1 release?

-- 
Bye, Peter Korsgaard