spdk.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sasha Kotchubievsky <sashakot at dev.mellanox.co.il>
To: spdk@lists.01.org
Subject: [SPDK] Re: Preparation for SPDK 19.10 release
Date: Wed, 16 Oct 2019 14:55:01 +0300	[thread overview]
Message-ID: <04f201d58418$8b4b7f40$a1e27dc0$@dev.mellanox.co.il> (raw)
In-Reply-To: 3FF20EF7F07495429158B858FACC0D7F4AC1B580@IRSMSX103.ger.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 2954 bytes --]

Hi Tomek,

That's great news. 

I have couple questions:

- Some of latest SPDK releases (18.10, 19.04, 19.07) were released with
serious bugs in NVME-OF RDMA. Especially latest 19.07. Is it possible to
wait with formal release till our group in Mellanox will verify release
candidate in internal verification system? I think, couple of days will be
enough for us provide a feedback to the community.
-  Can we add couple special sections to SPDK release notes
(https://github.com/spdk/spdk/releases/tag/v19.07) ? 
 	- Changes in interfaces
	- Changes in configuration parameters (including defaults)
	- Known bugs/issues
For customers building solution on SPDK and considering upgrade, it's
important to see changes in interfaces (including configuration parameters).


Example of changes in an interface in coming 19.10 is 
https://github.com/spdk/spdk/commit/9522ed36f8474c9314b76b2618e8d2d9de56afee
#diff-2c205ae4170cbd2bbf219969f03c9c8d
This commit adds a new  event to bdev interface.

One of commits changed defaults was
https://github.com/spdk/spdk/commit/b6b0a0ba59a21faf1a320dd3ea7079b282f9fc31
It changes default IOUnit size from 4K to 8K and affected existing
configurations.

From my experience, having a table/list in release notes with such changes
(interfaces, parameters) can help to users to understand side-effects of the
upgrade.
I would suggest to maintain the table in Changelog and ask for contributors
to update it is a part of patch. At release, this table can be just copied
to release notes.  

Best regards
Sasha

-----Original Message-----
From: Zawadzki, Tomasz <tomasz.zawadzki(a)intel.com> 
Sent: Wednesday, October 9, 2019 5:41 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] Preparation for SPDK 19.10 release

Hello all,

The merge window for SPDK 19.10 release will close by October 24th.
Please ensure all patches you believe should be included in the release are
merged to master branch by this date.
You can do it by adding a hashtag '19.10' in GerritHub on those patches.

The current set of patches that are tagged and need to be reviewed can be
seen here:
https://review.gerrithub.io/q/hashtag:%252219.10%2522+(status:open)

Starting with this release, process used so far for Maintenance releases
(ex. 19.04.1) will be applied to main releases. On October 24th new branch
'v19.10.x' will be created, and a patch on it will be tagged as release
candidate.
Then, on October 31th, a formal release will take place tagging the last
patch on the branch as SPDK 19.10.

Between release candidate and formal release, only critical fixes shall be
backported to the 'v19.10.x' branch.

Development can continue without disruptions on 'master' branch.

Thanks,
Tomek
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org

             reply	other threads:[~2019-10-16 11:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 11:55 Sasha Kotchubievsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-16 14:46 [SPDK] Re: Preparation for SPDK 19.10 release Luse, Paul E
2019-10-16 15:21 Harris, James R
2019-10-16 16:10 Sasha Kotchubievsky
2019-10-16 17:00 Sasha Kotchubievsky
2019-10-16 17:12 Harris, James R
2019-10-16 20:01 Luse, Paul E
2019-10-25  9:47 Zawadzki, Tomasz

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='04f201d58418$8b4b7f40$a1e27dc0$@dev.mellanox.co.il' \
    --to=spdk@lists.01.org \
    /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).