Hi Shyam,
On 09/11/2017 07:51 PM, 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
- 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
Sorry for the delay. I would like to propose below feature for 3.13
release -
gfapi: APIs needed to register cbk functions for upcalls
Summary: Instead of polling continuously for upcalls, we need APIs for
the applications to be able to register upcall events and the
corresponding callback functions to be invoked.
github issue: #315 [1]
Patch (under review): https://review.gluster.org/#/c/18349/
Please let me know if this can be targeted for 3.13 release.
Thanks,
Soumya
[1] https://github.com/gluster/glusterfs/issues/315
- 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
_______________________________________________
maintainers mailing list
maintainers@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/maintainers
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
