U-Boot v2018.09 was released on Mon, 10 September 2018. U-Boot v2018.11 was released on Thu, 15 November 2018. U-Boot v2019.01 was released on Mon, 14 January 2019. U-Boot v2019.04 was released on Mon, 08 April 2019. U-Boot v2019.07 was released on Mon, 08 July 2019. U-Boot v2019.10 was released on Mon, 07 October 2019. U-Boot v2020.01 was released on Mon, 06 January 2020. U-Boot v2020.04 was released on Mon, 13 April 2020. U-Boot v2020.07 was released on Mon, 06 July 2020. U-Boot v2020.10 was released on Mon, 05 October 2020. U-Boot v2021.01 was released on Mon, 11 January 2021. U-Boot v2021.04 was released on Mon, 05 April 2021.
U-Boot v2021.07 was released on Mon, 05 July 2021. U-Boot v2021.10 was released on Mon, 04 October 2021.
U-Boot v2022.01 was released on Mon, 10 January 2022. U-Boot v2022.04 was released on Mon, 04 April 2022. The U-Boot configuration can be found here. Note: these statistics are generated by a clone of Jonathan Corbet's gitdm script Please note that the following dates are for information only and without Release "v2022.10" is scheduled in -35 days - on 03 October 2022.The Merge Window for the next release (v2022.10) is open until -rc1 release on.U-Boot v2022.07 was released on Mon 11 July 2022.U-Boot v2010.09-rc1 - Release candidate 1 for September 2010 release U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree Regular releases are now identified by namesĬonsisting of the calendar year and month of the release date.Īdditional fields (if present) indicate release candidates orīug fix releases in "stable" maintenance trees. Numerical release numbers without deeper meaning The names of the releases were changed from Starting with the release in October 2008, Which are documented in the u-boot documentation. There are differences in the actual procedures, Note 2: Even though we follow Linux ways in may respects, Without caring too much about the announced deadline.
#DENX U BOOT CODE#
The code will be released when it is considered ready Good reasons, for example if there are known bugs or other technical Not hesitate and take the liberty to delay a release if there are Note: While we try to adhere to the release schedule, we will After the merge window closes, no new features may be added to allow for a release candidate phase which is intended to fix bugs and regressions.Linus Torvalds explains here and there what the term "merge window" is supposed to mean. While this merge window is open, new features can be added to the U-Boot source tree. if the release was on a Monday, then the merge window will close on the Monday in the 3rd week after the release. Immediately following each release, there will be a "merge window" of normally 21 days, i.
The U-Boot projects attempts to maintain a fixed, predictable Release
0 kommentar(er)
