Re: [Gluster-users] Gluster Community Meeting 2016-02-01

2017-02-14 Thread Kaushal M 
On Wed, Feb 1, 2017 at 12:37 AM, Vijay Bellur  wrote:
> Adding URL for meeting pad.
>
> On Tue, Jan 31, 2017 at 12:41 PM, Kaushal M  wrote:
>>
>> Hi all,
>>
>> This is a reminder for tomorrows community meeting. The meeting is
>> scheduled to be held in #gluster-meeting on Freenode at 1500UTC.
>>
>> Please add your updates for the last two weeks and any topics for
>> discussion into the meeting pad at [1].
>>
>> ~kaushal
>>
>
>
> [1]
> https://hackmd.io/CwBghmCsCcDGBmBaApgDlqxwBMYDMiqkqS0wxAjAEbLIDssVIQA=?both#

Here are the meeting notes from the Community meeting on 2017-02-01.
I should have sent this out 2 weeks back, but in between all the
travelling, I forgot. Sorry about that.

We had quite a lively discussion on two topics. jdarcy started a
discussion around policies for reverting patches, and shyam started a
discussion around the 3.10 release and the non responsiveness of
contributors. More details can be found in the meeting minutes and
logs below.

The next meeting is on 15th February at 1500 UTC. Remember to add your
updates to the meeting notepad at
https://bit.ly/gluster-community-meetings

Cheers!
~kaushal

- Minutes: 
https://meetbot.fedoraproject.org/gluster-meeting/2017-02-01/community_meeting_2017-02-01.2017-02-01-15.00.html
- Minutes (text):
https://meetbot.fedoraproject.org/gluster-meeting/2017-02-01/community_meeting_2017-02-01.2017-02-01-15.00.txt
- Log: 
https://meetbot.fedoraproject.org/gluster-meeting/2017-02-01/community_meeting_2017-02-01.2017-02-01-15.00.log.html

## Topics of Discussion

The meeting is an open floor, open for discussion of any topic entered below.

- Policy on reverting patches that are found to cause spurious test
failures (jdarcy)
- One change got merged (driven by downstream pressure), that
caused test failures for all future patches, and held up merges
- Two proposals for addressing such issues
- Revert said patches
- Also revoke commit permissions for habitual offenders
- Reverting bad patches is good.
- Infra support is required for making this easier
- jdarcy will reach out to nigelb to make this possible
- Revoking commit permissions needs to have a much larger
discussion only on that
- JoeJulian suggested a gfapi based test harness for per xlator testing
- 3.10 TODO nag in the community meeting
- There are a few TODOs that contributors are not responding to,
need some urgency here
- Reviews, release-notes, backport requests, among possibly others
- Just want to shout out in the meeting on this!
- Swapping reviews could help
- But most reviews happen within a component, so reviews
generally cannot be swapped
- We should encourage cross component reviews
- Contributors need to be educated that doing this is important
- Most of the discussions in IRC and mailing-lists don't seem
to reach contributors
- Probably due to a lot of noise
- Maintainers need to take up the responsibility of educating
their teams that upstream contribution isn't only submitting patches
- Immediate actions for 3.10
- Someone in bangalore will physically call on developers to
get stuff done



### Next edition's meeting host

- kshlm

## Updates

> NOTE : Updates will not be discussed during meetings. Any important or 
> noteworthy update will be announced at the end of the meeting

### Action Items from the last meeting

- rastar will start a conversation on gluster-devel about 3.10 blocker
  test bugs.
- [update] sent today on feb 1st

### Releases

 GlusterFS 4.0

- Tracker bug :
https://bugzilla.redhat.com/showdependencytree.cgi?id=glusterfs-4.0
- Roadmap : https://www.gluster.org/community/roadmap/4.0/
- Updates:
  - GD2
  - 
https://lists.gluster.org/pipermail/gluster-devel/2017-February/052016.html
  - Volfile fetch supported now

 GlusterFS 3.10

- Maintainers : shyam, kkeithley, rtalur
- Next release : 3.10.0
- Target date: February 21, 2017 (this has slipped to accommodate
brick multiplexing feature)
- Release tracker : https://github.com/gluster/glusterfs/milestone/1
- Updates:
  - In the process of preparing release-notes to release beta1
  - beta1 target date is currently 1st Feb, 2017, and we are tracking
a day by day slip on this
  - Expect a possible 1 more day delay as we still are not getting
healthy responses from contributors on various activities
  - Please try and prioritize 3.10 work

 GlusterFS 3.9

- Maintainers : pranithk, aravindavk, dblack
- Current release : 3.9.1
- Next release : 3.9.2
  - Release date : 20 February 2017 (if 3.10 hasn't shipped by then)
- Tracker bug : https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.9.2
- Open bugs : 
https://bugzilla.redhat.com/showdependencytree.cgi?maxdepth=2=glusterfs-3.9.2_resolved=1
- Roadmap : https://www.gluster.org/community/roadmap/3.9/
- Updates:
  - _Add updates here_

 GlusterFS 3.8

-

Re: [Gluster-users] Gluster Community Meeting 2016-02-01

2017-01-31 Thread Vijay Bellur 
Adding URL for meeting pad.

On Tue, Jan 31, 2017 at 12:41 PM, Kaushal M  wrote:

> Hi all,
>
> This is a reminder for tomorrows community meeting. The meeting is
> scheduled to be held in #gluster-meeting on Freenode at 1500UTC.
>
> Please add your updates for the last two weeks and any topics for
> discussion into the meeting pad at [1].
>
> ~kaushal
>
>

[1]
https://hackmd.io/CwBghmCsCcDGBmBaApgDlqxwBMYDMiqkqS0wxAjAEbLIDssVIQA=?both#
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Gluster Community Meeting 2016-02-01

2017-01-31 Thread Kaushal M 
Hi all,

This is a reminder for tomorrows community meeting. The meeting is
scheduled to be held in #gluster-meeting on Freenode at 1500UTC.

Please add your updates for the last two weeks and any topics for
discussion into the meeting pad at [1].

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