[Gluster-devel] GlusterFS 3.5 planning

[Amar Tumballi]

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/4778and dependencies)

glusterd: Calculate volume op-versions only on
set/reset<http://review.gluster.org/5568>
build: Start using library versioning for various
libraries<http://review.gluster.org/5645>
cli,glusterd: Implement 'volume status tasks'<http://review.gluster.org/6006>
glusterd: Set errstr appropriately on peer op
failure<http://review.gluster.org/5978>
geo-rep: logrotate: Logrotate handling <http://review.gluster.org/5968>
glusterd: Fix storing volumes on setting global
opts<http://review.gluster.org/6007>
libglusterfs: clean up for syncenv_new/destroy()<http://review.gluster.org/5838>
mount.glusterfs: getopts support and cleanup<http://review.gluster.org/5931> -
for man page cleanup :-)
glusterd: Validating invalid log-level under geo-rep config
options.<http://review.gluster.org/5989>
protocol/client: Add explicit states for connection
sequence<http://review.gluster.org/5956>
protocol: add gfid to on wire format for
fsetattr/rchecksum<http://review.gluster.org/3956>
features/changelog : Improvement in changelog
"encoding-change".<http://review.gluster.org/5844>


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 <http://review.gluster.org/5327>
cluster/afr: refactoring and cleanup of AFR code<http://review.gluster.org/6010>
glusterd: Volume locks and transaction specific
opinfos<http://review.gluster.org/5994>
gfapi: object handle based API extensions <http://review.gluster.org/5936>
cli,glusterd: Changes to cli-glusterd
communication<http://review.gluster.org/5280>
client_t: phase 2, refactor server_ctx and locks_ctx
out<http://review.gluster.org/5678>
glusterd: glusterd changes to quota. <http://review.gluster.org/6003> (and
dependent patches)
features/qemu-block: add qemu backing image support
(clone)<http://review.gluster.org/5967>
cli: Introduce syncop in cli <http://review.gluster.org/4726>
bd: Add support to create thin LV <http://review.gluster.org/5234> (and
dependent patches)
gfid-access: do chown() after creating the new
entries<http://review.gluster.org/5833>

Good to have :

features/compress: Compression/DeCompression
translator<http://review.gluster.org/3251>
mgmt/glusterd: check whether quorum has been met from
glusterd<http://review.gluster.org/5998>
libglusterfs/inode: introduce new APIs for ctx
handling<http://review.gluster.org/5890>
cluster/dht - rebalance: handle the rebalance @ inode level (!fd
level)<http://review.gluster.org/5891>
protocol/server: do not do root-squashing for trusted
clients<http://review.gluster.org/4863>
rpc,glusterd: Use rpc_clnt notifyfn to cleanup
mydata<http://review.gluster.org/5512>


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 at gmail.com> wrote:

>
>
>
> On Wed, Jul 24, 2013 at 11:00 PM, Vijay Bellur <vbellur at redhat.com> 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<http://www.gluster.org/community/documentation/index.php/Planning35>
>> [2] http://www.gluster.org/**community/documentation/index.**
>> php/Planning35#Proposing_New_**Features<http://www.gluster.org/community/documentation/index.php/Planning35#Proposing_New_Features>
>>
>>
>>
>> ______________________________**_________________
>> Gluster-devel mailing list
>> Gluster-devel at nongnu.org
>> https://lists.nongnu.org/**mailman/listinfo/gluster-devel<https://lists.nongnu.org/mailman/listinfo/gluster-devel>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20130928/594dca7e/attachment-0001.html>