On Wed, 1 Nov 2017 at 00:14, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
On Tue, 31 Oct 2017 at 18:34, Shyam Ranganathan <srangana@xxxxxxxxxx> wrote:On 10/31/2017 08:11 AM, Karthik Subrahmanya wrote:
> Hey Shyam,
>
> Can we also have the heal info summary feature [1], which is merged
> upstream [2].
> I haven't raised an issue for this yet, I can do that by tomorrow and I
> need to write a doc for that.
Thanks for bringing this to my notice, it would have been missed out as
a feature otherwise.
I do see that the commit start goes way back into 2015, and was
rekindled in Sep 2017 (by you), because I was initially thinking why
this did not have a issue reference anyway to begin with.
Please raise a github issue for the same with the appropriate details
and I can take care of the remaining process there for you.
@maintainers on the patch review, please ensure that we have a github
reference for features, else there is a lot we will miss for the same!This was a miss from my end where I should have checked the corresponding issue id in the patch. Apologies!
Can we have a job to check if a bugzilla is used upstream against a patch which has a FutureFeature as a keyword, we fail such jobs to automate such misses not to happen? And then RFEs can be closed using github references?
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1261463
> [2] https://review.gluster.org/#/c/12154/
>
>
> Thanks & Regards,
> Karthik
_______________________________________________
maintainers mailing list
maintainers@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/maintainers
--- Atin (atinm)
--
- Atin (atinm)
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel