On Wed, Jan 11, 2017 at 9:32 AM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
On Mon, Jan 9, 2017 at 1:56 PM, Samikshan Bairagya <sbairagy@xxxxxxxxxx> wrote:
On 01/09/2017 10:33 AM, Shyam wrote:
I am considering this as tentatively accepted for 3.10 release for the
following reasons,
- It is part of user feedback received during discussion of a related
and targeted feature for 3.10 [1]
- Feature is useful and enhancement as analyzed by the glusterd team
is relevant
- Code is ready and partly reviewed
It is tentative, so that in case others have objections in changing the
3.10 scope to add this, we can consider hear them out. I would hence
wait for a couple of days before merging this into master before
branching for 3.10. (say till Jan 11th, 2017)
Issue for this is already created here [2], could you accelerate adding
a feature page for the same?
The feature page for the same can be found here: http://review.gluster.org/16359/ spec change has got my ack, however given I don't have merge rights on the spec, would request Kaushal/Shyam to get this in. Also the patch http://review.gluster.org/#/c/16303/ has been acked with +2.
spec change is now merged, thank Pai! I'll be merging the other change request by today EOD, if you have any objections please raise it early.
Thanks,
Samikshan
______________________________
Thanks,
Shyam
[1] https://github.com/gluster/glusterfs/issues/56
[2] https://github.com/gluster/glusterfs/issues/79
On 01/06/2017 05:29 PM, Atin Mukherjee wrote:
This would definitely be a great addition looking at the past user______________________________
requests and bugs. I already have acked the patch and awaiting Pranith's
review.
@Samikshan - Can we file a github issue for the same (with a spec) and
then if it's approved we can put it in release-3.10 lane?
On Fri, Jan 6, 2017 at 4:34 PM, Samikshan Bairagya <sbairagy@xxxxxxxxxx
<mailto:sbairagy@xxxxxxxxxx>> wrote:
Hi all,
This patch, http://review.gluster.org/#/c/16303/
<http://review.gluster.org/#/c/16303/ > adds details on maximum
supported op-version for clients to the volume status <VOLNAME|all>
output. This might be a useful change to have as part of the
upcoming 3.10 release and I would like to request the respective
maintainers to consider the same.
https://bugzilla.redhat.com/show_bug.cgi?id=1409078
<https://bugzilla.redhat.com/show_bug.cgi?id=1409078 > is the
corresponding BZ for this change.
Thanks and Regards,
Samikshan
_______________________________________________
maintainers mailing list
maintainers@xxxxxxxxxxx <mailto:maintainers@xxxxxxxxxxg >
http://www.gluster.org/mailman/listinfo/maintainers
<http://www.gluster.org/mailman/listinfo/maintainers >
--
~ Atin (atinm)
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
--~ Atin (atinm)
--
~ Atin (atinm)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
