[Gluster-Maintainers] Release 3.12: Status of features (Require responses!)

[Shyam]

Hi,

Prepare for a lengthy mail, but needed for the 3.12 release branching, 
so here is a key to aid the impatient,

Key:
1) If you asked for an exception to a feature (meaning delayed backport 
to 3.12 branch post branching for the release) see "Section 1"
   - Handy list of nick's that maybe interested in this:
     - @pranithk, @sunilheggodu, @aspandey, @amarts, @kalebskeithley, 
@kshlm (IPv6), @jdarcy (Halo Hybrid)

2) If you have/had a feature targeted for 3.12 and have some code posted 
against the same, look at "Section 2" AND we want to hear back from you!
   - Handy list of nick's that should be interested in this:
     - @csabahenk, @nixpanic, @aravindavk, @amarts, @kotreshhr, 
@soumyakoduri

3) If you have/had a feature targeted for 3.12 and have posted no code 
against the same yet, see "Section 3", your feature is being dropped 
from the release.
   - Handy list of nick's that maybe interested in this:
     - @sanoj-unnikrishnan, @aravindavk, @kotreshhr, @amarts, @jdarcy, 
@avra (people who filed the issue)

4) Finally, if you do not have any features for the release pending, 
please help others out reviewing what is still pending, here [1] is a 
quick link to those reviews.

Sections:

******Section 1:******
Exceptions granted to the following features: (Total: 8)
Reasons:
   - Called out in the mail sent for noting exceptions and feature 
status for 3.12
   - Awaiting final changes/decision from a few Facebook patches

Issue list:
- Implement an xlator to delay fops
   - https://github.com/gluster/glusterfs/issues/257

- Implement parallel writes feature on EC volume
   - https://github.com/gluster/glusterfs/issues/251

- DISCARD support with EC
   - https://github.com/gluster/glusterfs/issues/254

- Cache last stripe of an EC volume while write is going on
   - https://github.com/gluster/glusterfs/issues/256

- gfid-path by default
   - https://github.com/gluster/glusterfs/issues/139

- allow users to enable used of localtime instead of UTC for log entries
   - https://github.com/gluster/glusterfs/issues/272

- Halo translator: Hybrid mode
   - https://github.com/gluster/glusterfs/issues/217

- [RFE] Improve IPv6 support in GlusterFS
   - https://github.com/gluster/glusterfs/issues/192

******Section 2:******
Issues needing some further clarity: (Total: 6)
Reason:
   - There are issues here, for which code is already merged (or 
submitted) and issue is still open. This is the right state for an issue 
to be in this stage of the release, as documentation or release-notes 
would possibly be still pending, which will finally close the issue (or 
rather mark it fixed)
   - BUT, without a call out from the contributors that required code is 
already merged in, it is difficult to assess if the issue should qualify 
for the release

Issue list:
- [RFE] libfuse rebase to latest?
   - https://github.com/gluster/glusterfs/issues/153
   - @csabahenk is this all done?

- Decide what to do with glfs_ipc() in libgfapi
   - https://github.com/gluster/glusterfs/issues/269
   - @nixpanic I assume there is more than just test case disabling for 
this, is this expected to happen by 3.12?

- Structured log format support for gf_log and gf_msg
   - https://github.com/gluster/glusterfs/issues/240
   - @aravindavk this looks done, anything code wise pending here?

- xxhash: Add xxhash library
   - https://github.com/gluster/glusterfs/issues/253
   - @kotreshhr this looks done, anything code wise pending here?

- posix: provide option to handle 'statfs()' properly when more than 1 
brick is exported from 1 node
   - https://github.com/gluster/glusterfs/issues/241
   - @amarts patch is still awaiting reviews, should this be tracked as 
an exception?

- gfapi to support leases and lock-owner
   - https://github.com/gluster/glusterfs/issues/213
   - @soumyakoduri I do not see work progressing on the patches 
provided, should this be dropped from 3.12?

******Section 3:******
Issues moved out of the 3.12 Milestone: (Total: 8)
Reasons:
   - No commits visible against the github issue
   - No commits against 'master' branch visible on the github issue

Further changes:
   - No new milestone assigned, IOW not moved to 4.0 by default, hence 
contributors working on these features would need to rekindle 
conversations on including the same in 4.0 on the ML or on the issue itself.

Issue List:
- [RFE] Syslog alert when Geo-rep worker is faulty for a configurable time
   https://github.com/gluster/glusterfs/issues/226

- [RFE] Geo-rep: Sync metadata operations as part of sync itself 
(rsync/tar-ssh)
   https://github.com/gluster/glusterfs/issues/222

- Provide support for clearing translator specific inode contex / 
forgetting inode (for supportability)
   - https://github.com/gluster/glusterfs/issues/249

- [RFE]: ctime generator xlator
   - https://github.com/gluster/glusterfs/issues/208

-  Introduce force option for Snapshot Restore
   - https://github.com/gluster/glusterfs/issues/62

- rpc-clnt reconnect timer
   - https://github.com/gluster/glusterfs/issues/152

- bug: read-only xlator doesn't implement fallocate
   - https://github.com/gluster/glusterfs/issues/187

- Fix or eliminate synctasks
   - https://github.com/gluster/glusterfs/issues/144

Thanking in advance for all the responses, so help cleanup and chase the 
right reviews and features for the release.

Shyam & Jiffin

[1] Review focus: 
https://review.gluster.org/#/q/starredby:srangana%2540redhat.com