[Gluster-devel] EC Stripe cache jobs

[Nigel Babu]

Hello,

We have a job that tries to turn on stripe cache and run EC tests. It looks
like we recently made the decision to turn on stripe cache by default. Is
this job needed anymore? It fails at the moment due to a merge conflict.


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

Re: [Gluster-devel] [Gluster-users] Release 3.12.8: Scheduled for the 12th of April

[Ravishankar N]

Mabi,

It looks like one of the patches is not a straight forward cherry-pick 
to the 3.12 branch. Even though the conflict might be easy to resolve, I 
don't think it is a good idea to hurry it for tomorrow. We will 
definitely have it ready by the next minor release (or if by chance the 
release is delayed and the back port is reviewed and merged before 
that). Hope that is acceptable.


-Ravi

On 04/11/2018 01:11 PM, mabi wrote:

Dear Jiffin,

Would it be possible to have the following backported to 3.12:

https://bugzilla.redhat.com/show_bug.cgi?id=1482064



See my mail with subject "New 3.12.7 possible split-brain on replica 
3" on the list earlier this week for more details.


Thank you very much.

Best regards,
Mabi

‐‐‐ Original Message ‐‐‐
On April 11, 2018 5:16 AM, Jiffin Tony Thottan  
wrote:



Hi,

It's time to prepare the 3.12.8 release, which falls on the 10th of
each month, and hence would be 12-04-2018 this time around.

This mail is to call out the following,

1) Are there any pending *blocker* bugs that need to be tracked for
3.12.7? If so mark them against the provided tracker [1] as blockers
for the release, or at the very least post them as a response to this
mail

2) Pending reviews in the 3.12 dashboard will be part of the release,
*iff* they pass regressions and have the review votes, so use the
dashboard [2] to check on the status of your patches to 3.12 and get
these going

3) I have made checks on what went into 3.10 post 3.12 release and if
these fixes are already included in 3.12 branch, then status on this 
is *green*

as all fixes ported to 3.10, are ported to 3.12 as well.

@Mlind

IMO https://review.gluster.org/19659 is like a minor feature to me. 
Can please provide a justification for why it need to include in 3.12 
stable release?


And please rebase the change as well

@Raghavendra

The smoke failed for https://review.gluster.org/#/c/19818/. Can 
please check the same?


Thanks,
Jiffin

[1] Release bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.12.8

[2] 3.12 review dashboard:
https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:3-12-dashboard




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


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

Re: [Gluster-devel] Release 4.1: Schedule, scope and review focus

[Shyam Ranganathan]

On 03/27/2018 02:59 PM, Shyam Ranganathan wrote:
> Hi,
> 
> As we have completed potential scope for 4.1 release (reflected here [1]
> and also here [2]), it's time to talk about the schedule.
> 
> - Branching date (and hence feature exception date): Apr 16th

We are about 5 days away from branching, now would be a good time to
think which features are slipping and call them out sooner than later!

> - Week of Apr 16th release notes updated for all features in the release
> - RC0 tagging: Apr 23rd
> - Week of Apr 23rd, upgrade and other testing
> - RCNext: May 7th (if critical failures, or exception features arrive late)
> - RCNext: May 21st
> - Week of May 21st, final upgrade and testing
> - GA readiness call out: May, 28th
> - GA tagging: May, 30th
> - +2-4 days release announcement
> 
> and, review focus. As in older releases, I am starring reviews that are
> submitted against features, this should help if you are looking to help
> accelerate feature commits for the release (IOW, this list is the watch
> list for reviews). This can be found handy here [3].
> 
> So, branching is in about 4 weeks!
> 
> Thanks,
> Shyam
> 
> [1] Issues marked against release 4.1:
> https://github.com/gluster/glusterfs/milestone/5
> 
> [2] github project lane for 4.1:
> https://github.com/gluster/glusterfs/projects/1#column-1075416
> 
> [3] Review focus dashboard:
> https://review.gluster.org/#/q/starredby:srangana%2540redhat.com
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Coverity covscan for 2018-04-11-909e2cdf (master branch)

[staticanalysis]

GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-04-11-909e2cdf
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel