> If we should backport more changes please create a pull request on > github, send a patch with the 22.03 or 21.02 prefix to the mailing list > or send a mail with a link to the master commit we should backport as an > answer to this mail and I will have a look at the commit.
How should simple github PRs that are intended be applied to both /master and /openwrt-22.03 be handled? (Where the long way would be: first open a PR to /master then come back and open another PR to cherry-pick back to /openwrt-22.03) Thanks On Mon, Mar 27, 2023 at 11:57 PM Hauke Mehrtens <ha...@hauke-m.de> wrote: > > Hi, > > I would like to create a new OpenWrt 22.03 and 21.02 minor release in > the next week. > > OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series. > > On github the following pull requests are tagged for the releases: > https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F22.03 > https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F21.02 > > If we should backport more changes please create a pull request on > github, send a patch with the 22.03 or 21.02 prefix to the mailing list > or send a mail with a link to the master commit we should backport as an > answer to this mail and I will have a look at the commit. > > Hauke > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
