Re: GlusterFS 3.5 planning

[Amar Tumballi <amarts@xxxxxxxxx>]

Set of patches I propose we take it in for release-3.5 (already passed regression test, and at least 1 review)

Graph cleanup patches from Raghavendra Bhat (http://review.gluster.org/4778 and dependencies)

glusterd: Calculate volume op-versions only on set/reset

build: Start using library versioning for various libraries

cli,glusterd: Implement 'volume status tasks'

glusterd: Set errstr appropriately on peer op failure

geo-rep: logrotate: Logrotate handling

glusterd: Fix storing volumes on setting global opts

libglusterfs: clean up for syncenv_new/destroy()

mount.glusterfs: getopts support and cleanup - for man page cleanup :-)

glusterd: Validating invalid log-level under geo-rep config options.

protocol/client: Add explicit states for connection sequence

protocol: add gfid to on wire format for fsetattr/rchecksum

features/changelog : Improvement in changelog "encoding-change".

Set of patches which would be good to have (sort of features, and also would need rebase if above set of patches go in)

glusterfs: zerofill support

cluster/afr: refactoring and cleanup of AFR code

glusterd: Volume locks and transaction specific opinfos

gfapi: object handle based API extensions

cli,glusterd: Changes to cli-glusterd communication

client_t: phase 2, refactor server_ctx and locks_ctx out

glusterd: glusterd changes to quota. (and dependent patches)

features/qemu-block: add qemu backing image support (clone)

cli: Introduce syncop in cli

bd: Add support to create thin LV (and dependent patches)

gfid-access: do chown() after creating the new entries

Good to have :

features/compress: Compression/DeCompression translator

mgmt/glusterd: check whether quorum has been met from glusterd

libglusterfs/inode: introduce new APIs for ctx handling

cluster/dht - rebalance: handle the rebalance @ inode level (!fd level)

protocol/server: do not do root-squashing for trusted clients

rpc,glusterd: Use rpc_clnt notifyfn to cleanup mydata

This may not be complete list. But would love to see patches listed here are considered.

Regards,

Amar

On Fri, Sep 27, 2013 at 11:50 PM, Amar Tumballi <amarts@xxxxxxxxx> wrote:

On Wed, Jul 24, 2013 at 11:00 PM, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:

Hi All,

We are considering a 4 month release cycle for GlusterFS 3.5. The tentative dates are as under:

14th Aug, 2013 - Feature proposal freeze

4th Oct, 2013 - Feature freeze & Branching

Considering the Feature freeze date is approaching, it would be great if developers wishing their features get it pushed up with reviewers (and not just maintainers).

Would be great if people rebase their patches so it shows up at the top :-)

-Amar

 

10th Oct, 2013 - Community Test Day1

29th Oct, 2013 - 3.5.0 Beta Release

31st Oct, 2013 - Community Test Day2

2nd Dec, 2013 - 3.5.0 GA

The planning page for 3.5 is at [1]. New features can be proposed at [2]. After the proposal freeze, we can slot proposed projects into "core" and "nice to have" feature buckets in the planning page over an IRC meeting.

Please do chime in with your thoughts on planning and propose features for addition to GlusterFS 3.5.

Cheers,
Vijay

[1] http://www.gluster.org/community/documentation/index.php/Planning35
[2] http://www.gluster.org/community/documentation/index.php/Planning35#Proposing_New_Features



_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
https://lists.nongnu.org/mailman/listinfo/gluster-devel