On 09/11/2017 10:21 AM, Shyam Ranganathan wrote:
Hi,
The next community release of Gluster is 3.13, which is a short term
maintenance release is slated for release on 30th Nov [1] [2]. Thus
giving a 2 month head room to get to 4.0 work done, while maintaining
the cadence of releasing every 3 months.
This mail is to announce the scope, schedule and request contributors
for the features that will make it to 3.13.
1) Scope:
3.13 is expected to be *lean* in scope, as most work is expected to be
around 4.0 in the coming months. This STM can be considered as a sneak
peek for some 4.0 features, that will *not* break any compatibility in
the 3.x release line.
2) The release calendar looks as follows,
- Feature proposal end date: Sep-22-2017
- Branching: Oct-16-2017
3.13 was not branched on time, primarily due to lack of attention from
my side.
I am planning on branching the release tomorrow (1st Nov 2017 @ 11:00 PM
UTC) and as such have the following features in master that will be a
part of this release, and need some information from the respective
feature owners.
1) Initial versions of GFProxy, possibly tech preview (issue #242)
- Announced in the summit, so I made some changes to the issue in github
- @poornimag are all things tech preview related already in the code?
2) Data corruption in write ordering of rebalance and application writes
(issue #308)
- @raghavendrahg will this be ready in time before the branching?
<items from here are either ready or done and there are no further
details needed at present>
3) Include details about memory pools in statedumps (issue #307)
4) posix: provide an option to reserve backend storage space (issue #236)
5) Have max-port range in glusterd.vol (issue #305)
6) snpashots issues with other processes accessing the mounted brick
snapshots (issue #276)
7) List all the connected clients for brick and also exported bricks /
snaps from each brick process (issue #178)
8) gfapi: APIs needed to register cbk functions for upcalls (issue #315)
9) gfapi: new macros GLFS_XALLOC/GLFS_FREE adds a glfs_mem_header for
exported memory (issue #312)
10) Compilation warnings with gcc 7.x (issue #259) (partially fixed for
3.13)
- Release: Nov-30-2017
- Feature proposal:
- Contributors need to request for features that will be a part of
the 3.13 release, sending a mail to the devel list, and including the
github issue # for the feature
- Branching: date by when declared features (appearing in the release
lane, in the github project board [3]) need to be completed, incomplete
or features that are not ready by the branching date, would be pushed
out to the next release.
Thanks,
Shyam
[1] Github milestone: https://github.com/gluster/glusterfs/milestone/6
[2] Release schedule: https://www.gluster.org/release-schedule/
[3] Github project board: https://github.com/gluster/glusterfs/projects/1
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
