Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

[Niels de Vos]

On Wed, Nov 01, 2017 at 06:56:02AM -0400, Shyam Ranganathan wrote:
> On 10/31/2017 02:52 PM, Atin Mukherjee wrote:
> > @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?
> 
> Is the keyword followed diligently, that we can rely on such a check?
> 
> Who adds the keyword to BZ in case others missed adding the same?
> 
> I ask, as I was unaware of this keyword myself.

We actually have the FutureFeature keyword documented in the bug
triaging guidelines:
  http://docs.gluster.org/en/latest/Contributors-Guide/Bug-Triage/

 > FutureFeature : This keyword is used for bugs which are used to
 > request for a feature enhancement ( RFE - Requested Feature
 > Enhancement) for future releases of GlusterFS. If you open a bug by
 > requesting a feature which you would like to see in next versions of
 > GlusterFS please report with this keyword.

Ideally, anyone working on bugs is aware of these and follows the
guidelines. Unfortunately we can not assume that is the case. Triaging
does not seem to happen as regurarely as when we had the weekly meetings
dedicated to this. The "Weekly Untriaged Bugs" email does require an
action from the developers working on the components, hopefully that
will be seen of higher importance with this email thread.

Latest example of the untriaged bugs email:
  http://lists.gluster.org/pipermail/gluster-devel/2017-October/053842.html

HTH,
Niels


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

[Shyam Ranganathan]

On 10/31/2017 02:52 PM, Atin Mukherjee wrote:

@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?


Is the keyword followed diligently, that we can rely on such a check?

Who adds the keyword to BZ in case others missed adding the same?

I ask, as I was unaware of this keyword myself.

Shyam
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

[Atin Mukherjee]

On Tue, 31 Oct 2017 at 18:34, Shyam Ranganathan  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!


>
> >
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1261463
> > [2] https://review.gluster.org/#/c/12154/
> >
> >
> > Thanks & Regards,
> > Karthik
>
> ___
> maintainers mailing list
> maintain...@gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers
>
-- 
- Atin (atinm)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

[Shyam Ranganathan]

On 09/27/2017 05:12 AM, Soumya Koduri wrote:

Hi Shyam,

On 09/11/2017 07:51 PM, Shyam Ranganathan wrote:

- Feature proposal:
   - Contributors need to request for features that will be a part of 
the 3.13 release, sending a mail to the devel list, and including the 
github issue # for the feature




Sorry for the delay.  I would like to propose below feature for 3.13 
release -


gfapi: APIs needed to register cbk functions for upcalls

Summary: Instead of polling continuously for upcalls, we need APIs for 
the applications to be able to register upcall events and the 
corresponding callback functions to be invoked.


github issue: #315 [1]

Patch (under review): https://review.gluster.org/#/c/18349/

Please let me know if this can be targeted for 3.13 release.


Yes, and thank you for posting this on the lists.

The milestone for the said issue is updates (to 3.13) and also the 
project lane for 3.13 is updated with this issue [2]




Thanks,
Soumya
[1] https://github.com/gluster/glusterfs/issues/315


[2] 3.13 project lane: https://github.com/gluster/glusterfs/projects/1
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.13: (STM release) Details

[Soumya Koduri]

Hi Shyam,

On 09/11/2017 07:51 PM, Shyam Ranganathan wrote:

Hi,

The next community release of Gluster is 3.13, which is a short term 
maintenance release is slated for release on 30th Nov [1] [2]. Thus 
giving a 2 month head room to get to 4.0 work done, while maintaining 
the cadence of releasing every 3 months.


This mail is to announce the scope, schedule and request contributors 
for the features that will make it to 3.13.


1) Scope:
3.13 is expected to be *lean* in scope, as most work is expected to be 
around 4.0 in the coming months. This STM can be considered as a sneak 
peek for some 4.0 features, that will *not* break any compatibility in 
the 3.x release line.


2) The release calendar looks as follows,
- Feature proposal end date: Sep-22-2017
- Branching: Oct-16-2017
- Release: Nov-30-2017

- Feature proposal:
   - Contributors need to request for features that will be a part of 
the 3.13 release, sending a mail to the devel list, and including the 
github issue # for the feature




Sorry for the delay.  I would like to propose below feature for 3.13 
release -


gfapi: APIs needed to register cbk functions for upcalls

Summary: Instead of polling continuously for upcalls, we need APIs for 
the applications to be able to register upcall events and the 
corresponding callback functions to be invoked.


github issue: #315 [1]

Patch (under review): https://review.gluster.org/#/c/18349/

Please let me know if this can be targeted for 3.13 release.

Thanks,
Soumya
[1] https://github.com/gluster/glusterfs/issues/315


- Branching: date by when declared features (appearing in the release 
lane, in the github project board [3]) need to be completed, incomplete 
or features that are not ready by the branching date, would be pushed 
out to the next release.


Thanks,
Shyam

[1] Github milestone: https://github.com/gluster/glusterfs/milestone/6
[2] Release schedule: https://www.gluster.org/release-schedule/
[3] Github project board: https://github.com/gluster/glusterfs/projects/1
___
maintainers mailing list
maintain...@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel