test suite reviews and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: "announce@dpdk.org" <announce@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>,
	"ci@dpdk.org" <ci@dpdk.org>,
	"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: [dts] Patchwork upgrade
Date: Thu, 18 Feb 2021 14:36:20 +0000	[thread overview]
Message-ID: <MWHPR12MB147259D5575E3BAD12ECC670DA859@MWHPR12MB1472.namprd12.prod.outlook.com> (raw)

Hi,

We are planning to upgrade the Patchwork instance (https://patches.dpdk.org) to version 2.2.3 on Sunday Feb 21 at 4:00 AM PT. Please expect that Patchwork will temporarily be unavailable for a few minutes around that time.

The new release includes multiple features, performance improvements and bug fixes.
Patch and series pages will now include a link to the corresponding archive in https://inbox.dpdk.org.
The API version was updated to v1.2, so please update your scripts if you previously specified an older version explicitly.
The URL schema will be based on message IDs rather than patch IDs. URLs with patch IDs will be redirected to the new format.
After the upgrade, we will enable sending notification emails for patch state changes to submitters.

Please see the release notes:
https://patchwork.readthedocs.io/en/latest/releases/flannel/

Regards,
Ali

                 reply	other threads:[~2021-02-18 14:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR12MB147259D5575E3BAD12ECC670DA859@MWHPR12MB1472.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=aconole@redhat.com \
    --cc=announce@dpdk.org \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=dts@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).