Lines Matching refs:be

28 Any release of DPDK can be designated as a Stable Release if a
31 If a version is to be a "Stable Release", it should be designated as such
37 The duration of a stable is one complete release cycle (3 months). It can be
39 or if users supply backported fixes, however the explicit commitment should be
43 bugfixes and the criticality of the bugs. Releases should be coordinated with
50 A stable release can be designated as an LTS release based on community
52 year's November (X.11) release will be maintained as an LTS for 2 years.
54 After the X.11 release, an LTS branch will be created for it at
55 https://git.dpdk.org/dpdk-stable where bugfixes will be backported to.
60 It is anticipated that there will be at least 4 releases per year of the LTS
61 or approximately 1 every 3 months. However, the cadence can be shorter or
63 fixes. Releases should be coordinated with the validation engineers to ensure
69 At the end of the 2 years, a final X.11.N release will be made and at that
70 point the LTS branch will no longer be maintained with no further releases.
73 What changes should be backported
76 Backporting should be limited to bug fixes. All patches accepted on the main
77 branch with a Fixes: tag should be backported to the relevant stable/LTS
79 they will be discussed on the mailing lists.
96 Features should not be backported to stable releases. It may be acceptable, in
112 should also be CCed to the `[email protected] <https://mails.dpdk.org/listinfo/stable>`_
119 A Stable Release will be released by: