diff options
| author | Shyam <srangana@redhat.com> | 2017-07-21 16:52:59 -0400 |
|---|---|---|
| committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2017-07-21 21:17:36 +0000 |
| commit | 0440a4a9e337184e26818ce1d8037607c6888618 (patch) | |
| tree | dd265bcdb359ed9e2cd318c242b7c4475d34c86a /doc | |
| parent | deed1ca53c3f37ca8bd36412eed5fae55886a318 (diff) | |
doc: Initial template release notes for 3.12.0
Added an initial template for release notes for the 3.12.0
release.
This is in an attempt to provide an early editable copy for other
contribtors to get release notes earlier than usual for a release.
Change-Id: I0c6f259075ac2d6baac7b868473960cfc9d25d6d
BUG: 1473826
Signed-off-by: Shyam <srangana@redhat.com>
Reviewed-on: https://review.gluster.org/17853
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-notes/3.12.0.md | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/doc/release-notes/3.12.0.md b/doc/release-notes/3.12.0.md new file mode 100644 index 00000000000..94f97d12c14 --- /dev/null +++ b/doc/release-notes/3.12.0.md @@ -0,0 +1,39 @@ +# Release notes for Gluster 3.12.0 + +This is a major Gluster release that includes <TBD> ... + +The most notable features and changes are documented on this page. A full list +of bugs that have been addressed is included further below. + +## Major changes and features + +**NOTE to contributors: Copy the section below and add details regarding the +feature that you want to describe, and submit the work for review. See, +[older release notes](https://github.com/gluster/glusterfs/blob/release-3.11/doc/release-notes/3.11.0.md) for inspiration :)** + +**NOTE: Submit the note with the commit message referencing the github issue # +for the respective feature, as "Updates: gluster/glusterfs#N"*** + +### Feature one liner +**Notes for users:** + + +**Limitations:** + + +**Known Issues:** + + +## Major issues +1. Expanding a gluster volume that is sharded may cause file corruption + - Sharded volumes are typically used for VM images, if such volumes are + expanded or possibly contracted (i.e add/remove bricks and rebalance) there + are reports of VM images getting corrupted. + - The last known cause for corruption (Bug #1465123) has a fix with this + release. As further testing is still in progress, the issue is retained as + a major issue. + - Status of this bug can be tracked here, #1465123 + +## Bugs addressed + +Bugs addressed since release-3.11.0 are listed below.
\ No newline at end of file |