Handy to have some example links for easy copy'n'paste to check the final docs/tarball/git tree. Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- README | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/README b/README index 4252285..a4d7a75 100644 --- a/README +++ b/README @@ -164,4 +164,7 @@ Example: remote: 5e278012506c76d981e4283a92adec1c /srv/rel/dpdk-18.05.1.tar.xz +You can check the git tree to ensure everything looks good +- e.g. For DPDK 18.11 https://dpdk.org/browse/dpdk-stable/?h=18.11 + You want to prepare a change to the DPDK-web, so grab their repository. $ git clone git://dpdk.org/tools/dpdk-web @@ -169,14 +172,16 @@ You want to prepare a change to the DPDK-web, so grab their repository. Modify the file content/download/_index.md - update the tarball name - - check that the link to the documentation really has your tag listed - at the top left + - e.g. For DPDK 18.11.3 https://fast.dpdk.org/rel/dpdk-18.11.3.tar.xz - check that the downloadable tarball matches the md5 listed on the git push output - add that new md5 to the file + - check that the link to the documentation really has your tag listed + at the top left + - e.g. for DPDK 18.11 releases http://doc.dpdk.org/guides-18.11/ Modify the file content/roadmap/_index.md - update the stable releases table for the new versions and dates -and finally suggest the dpdk-web changes to the web team at web@dpdk.org +and finally send a patch for the dpdk-web changes to the web team at web@dpdk.org -- 2.21.0
Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- README | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README b/README index a4d7a75..fdf61ab 100644 --- a/README +++ b/README @@ -187,4 +187,5 @@ and finally send a patch for the dpdk-web changes to the web team at web@dpdk.or 6-announce-release +================== The last step is to announce it. The usage is also simpler: just type the @@ -194,3 +195,23 @@ too short and simple so far :). + +Security Releases +================= + +Just a reminder any comms to DPDK security team should be over encrypted email. + +For releases with embargoed CVEs steps 1/2/3/4 above will be skipped. + +Patches will be provided by the DPDK security team. They should be applied +locally and compile tested locally without using external tools like travis +that will make the patches public. + +For validation notes in step 5, they should be obtained from the author or +DPDK security team. + +In terms of sequence, the main thing is that everyone is ready and available. +Pushing different tags to the server can be done in series with other stable +maintainers to avoid any issues with tarball/docs generation. A single website +update can then be made. + That's all. -- 2.21.0
On Wed, 2019-11-13 at 16:51 +0000, Kevin Traynor wrote:
> Handy to have some example links for easy copy'n'paste
> to check the final docs/tarball/git tree.
>
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
> README | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
On Wed, 2019-11-13 at 16:51 +0000, Kevin Traynor wrote:
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
> README | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi