Re: Release 3.11: Pending features and reviews (2 days to branching)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 25, 2017 at 07:41:29PM -0400, Shyam wrote:
> Hi,
> 
> This mail should have been out 3-4 days earlier than now as branching is 2
> days away, but hopefully it is not too late.
> 
> The current release scope can be seen at [1].
> 
> If you do *not* recognize your nick in the following list then you can help
> us out by looking at pending reviews [2] and moving them along and
> optionally skip the rest of the mail.
> 
> If your nick is in the list below, please read along to update status on the
> action called out against you.
> 
> nick list: @amarts, @csabahenk, @ndevos, @pranith, @kaushal, @jiffin,
> @rabhat, @kaleb, @samikshan, @poornimag, @kotresh, @susant
> 
> If any reviews for the features listed below are still open and not
> appearing in [2] drop me a mail, and I will star it, so that it appears in
> the list as needed.
> 
> Status request of features targeted for 3.11:
> 
> 1) Starting with features that slipped 3.10 and were marked for 3.11
> 
> 1.1) In gfapi fix memory leak during graph switch #61
> @ndevos I know a series of fixes are up for review, will this be completed
> for this release, or would it be an ongoing effort across releases? If the
> latter, we possibly continue tracking this for the next release as well.

There are several fixes done, but it will be a topic that needs
continuing for the next few releases. Until we have a way to
automatically check for new problems and report bugs.

> 1.2) SELinux support for Gluster Volumes #55
> Latest reviews indicate this may be ready by branching, @jiffin or @ndevos
> will this make it by branching date?

We hope so! The two patches should be ready, fingers crossed:
 - https://review.gluster.org/6630
 - https://review.gluster.org/13762

...
> 3) New in 3.11 and not tracked in release scope [1] as there are no visible
> mail requests to consider these for 3.11 in the gluster devel lists
> 
> 3.1) Use standard refcounting functions #156
> @ndevos any updates? Should this be marked in the 3.11 scope?

Still an ongoing thing, we have *many* structures that cna benefit from
reference counting. Improvements like these are 'normal' maintenance
tasks IMHO.

Thanks,
Niels


> [1] Release scope: https://github.com/gluster/glusterfs/projects/1
> 
> [2] Reviews needing attention:
> https://review.gluster.org/#/q/status:open+starredby:srangana%2540redhat.com
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxxx
> http://lists.gluster.org/mailman/listinfo/gluster-devel

Attachment: signature.asc
Description: PGP signature

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

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux