| 3c60ea7b | 17-Jan-2024 |
Kevin Traynor <ktraynor@redhat.com> |
doc: update LTS maintenance to 3 years
The existing official policy was to maintain LTS releases for 2 years.
19.11 and 20.11 LTS releases were maintained for 3 years and there was
not significant
doc: update LTS maintenance to 3 years
The existing official policy was to maintain LTS releases for 2 years.
19.11 and 20.11 LTS releases were maintained for 3 years and there was
not significant issues caused by code divergence from main etc.
Update the policy to indicate 3 years maintenance for LTS releases, but
note that it depends on community support.
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Acked-by: Raslan Darawsheh <rasland@nvidia.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
Acked-by: Luca Boccassi <bluca@debian.org>
Acked-by: Xueming Li <xuemingl@nvidia.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
show more ...
|
| 96c0d4df | 02-Oct-2023 |
Bruce Richardson <bruce.richardson@intel.com> |
doc: update test contribution guidelines
With the Meson test suites being reworked to be automatically generated,
rather than having to be hard-coded in the meson.build file, we need to
update our c
doc: update test contribution guidelines
With the Meson test suites being reworked to be automatically generated,
rather than having to be hard-coded in the meson.build file, we need to
update our contributing guidelines to take account of this change.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
show more ...
|
| 20cb55cb | 10-Mar-2022 |
Luca Boccassi <luca.boccassi@microsoft.com> |
doc: relax requirement on commit messages of security fixes
Allow more flexibility with embargo lifting by not requiring
mentions of CVEs in commit messages if the lift date allows
it.
Signed-off-b
doc: relax requirement on commit messages of security fixes
Allow more flexibility with embargo lifting by not requiring
mentions of CVEs in commit messages if the lift date allows
it.
Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
show more ...
|
| 4f5adcc9 | 20-Oct-2023 |
Kevin Traynor <ktraynor@redhat.com> |
doc: add note about experimental API in LTS
The justification and impact for changing experimental API on LTS
branches is different from the main branch. So the policy that is
being used for allowin
doc: add note about experimental API in LTS
The justification and impact for changing experimental API on LTS
branches is different from the main branch. So the policy that is
being used for allowing experimental APIs to change is stricter on
the LTS branches.
This was not documented anywhere, so add some documentation.
Suggested-by: David Marchand <david.marchand@redhat.com>
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
show more ...
|
| 74913fd2 | 18-May-2023 |
Jerin Jacob <jerinj@marvell.com> |
doc: add process for new library approval in principle
Based on techboard meeting[1] action item, defining the process for a
new library approval in principle.
[1]
https://mails.dpdk.org/archives/d
doc: add process for new library approval in principle
Based on techboard meeting[1] action item, defining the process for a
new library approval in principle.
[1]
https://mails.dpdk.org/archives/dev/2023-January/260035.html
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
show more ...
|
| 5c9f84a8 | 20-Jul-2023 |
Bruce Richardson <bruce.richardson@intel.com> |
doc: add guidelines for logging, tracing and telemetry
As discussed by DPDK technical board [1], our contributor guide should
include some details as to when to use logging vs tracing vs telemetry
t
doc: add guidelines for logging, tracing and telemetry
As discussed by DPDK technical board [1], our contributor guide should
include some details as to when to use logging vs tracing vs telemetry
to provide the end user with information about the running process and
the DPDK libraries it uses.
[1] https://mails.dpdk.org/archives/dev/2023-March/265204.html
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Morten Brørup <mb@smartsharesystems.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
Acked-by: Huisong Li <lihuisong@huawei.com>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
show more ...
|
| e83d41f0 | 25-Nov-2022 |
Bruce Richardson <bruce.richardson@intel.com> |
mailmap: add list of contributors
Since a number of contributors to DPDK have submitted patches to DPDK
under more than one email address, we should maintain a mailmap file
to properly track their c
mailmap: add list of contributors
Since a number of contributors to DPDK have submitted patches to DPDK
under more than one email address, we should maintain a mailmap file
to properly track their commits using "shortlog",
and to do accurate automatic Cc with "get_maintainer.pl".
It also helps fix up any mangled names, for example, with
surname/firstname reversed, or with incorrect capitalization.
By keeping this file in the DPDK repository,
rather than committers maintaining their own copies,
it allows individual contributors to edit it
to update their own email address preferences if so desired.
While at it, update our checkpatches.sh script
and add some documentation to help new contributors.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
show more ...
|