Gluster users - Feb 2017 - Announcing release 3.11 : Scope, schedule and feature tracking

Hi,

With release 3.10 shipped [1], it is time to set the dates for release 
3.11 (and subsequently 4.0).

This mail has the following sections, so please read or revisit as needed,
   - Release 3.11 dates (the schedule)
   - 3.11 focus areas
   - 3.11 feature proposal changes (IMP: if you are proposing/delivering 
features 3.11 onward)
   - Release owners

We should be transitioning to using github for feature reporting and 
tracking, more fully from this release. So once again, if there exists 
any confusion on that front, reach out to the lists for clarification.

*Release 3.11 dates:*
Based on our release schedule [2], 3.11 would be 3 months from the 3.10 
release and would be a Short Term Maintenance (STM) release.

This puts 3.11 schedule as (working from the release date backwards):
- Release: May 30th, 2017
- Branching: April 27th, 2017

*3.11 focus areas:*
As maintainers of gluster, we want to harden testing around the various 
gluster features in this release. Towards this the focus area for this 
release are,

1) Testing improvements in Gluster
   - Primary focus would be to get automated test cases to determine 
release health, rather than repeating a manual exercise every 3 months
   - Further, we would also attempt to focus on maturing Glusto[7] for 
this, and other needs (as much as possible)

2) Merge all (or as much as possible) Facebook patches into master, and 
hence into release 3.11
   - Facebook has (as announced earlier [3]) started posting their 
patches mainline, and this needs some attention to make it into master

- We will still retain features that slipped 3.10 and hence were moved 
to 3.11 (see [4] for the list).

- We also are *not* stating *no* to net new features, so if there are 
any that you are working on do let us know if they will land by 3.11 
time frame.

*3.11 feature proposal changes:*
3.11 Roadmap is being tracked here [4], as was the case for 3.10.

To propose features for 3.11, here is a short how to,
   - Create an issue for the proposed feature in glusterfs github [5]

   - Propose and get your feature accepted for a release, by posting to 
gluster-devel at gluster.org with the relevant issue # and details

   - Use issue # in all commits against that feature (including commits 
to glusterdocs, glusterfs-specs and glusterfs repositories)

   - Reference the issue in commits, as ?Updates #n? or ?Fixes #n?, use 
Fixes with the last commit for the feature, so that when that gets 
merged, the issue is automatically closed

   - Reference the issue from non-glusterfs repositories as 
?{Fixes|Updates} gluster/gusterfs#n?

   - If a feature needs to be backported (which should ideally never 
happen) then create bugzilla for the same, and follow the bug workflow 
of backporting the same

A more detailed version on feature proposal and github usage for the 
same is present here [6]. This would get converted into gluster 
"Developer Guide" docs sometime soon.

*Release owners:*
   - Primary: Shyam <srangana at redhat.com>
   - Assisted by: <open, please volunteer>
   - Assisted by: <open, please volunteer>

Shyam

[1] 3.10 release announcement: 
http://lists.gluster.org/pipermail/gluster-devel/2017-February/052188.html

[2] Gluster release schedule: 
https://www.gluster.org/community/release-schedule/

[3] Mail regarding facebook patches: 
http://lists.gluster.org/pipermail/gluster-devel/2016-December/051784.html

[4] Release scope: https://github.com/gluster/glusterfs/projects/1

[5] glusterfs github issues: https://github.com/gluster/glusterfs/issues

[6] github issues for features and major fixes: 
https://hackmd.io/s/BkgH8sdtg#

[7] Glusto tests: https://github.com/gluster/glusto-tests

On 02/28/2017 08:47 PM, Shyam wrote:
> We should be transitioning to using github for feature reporting and 
> tracking, more fully from this release. So once again, if there exists 
> any confusion on that front, reach out to the lists for clarification.
I see that there was a discussion on this on the maintainers ML [1]. If 
it is not too late or if I may cast vote as a non-maintainer, I prefer 
to have bugzilla  for tracking bugs and the users ML for queries. I see 
many 'issues' on the github page which are mostly candidates for 
gluster-users ML.

Regards,

Ravi


[1] http://lists.gluster.org/pipermail/maintainers/2017-February/002195.html

On 02/28/2017 10:17 AM, Shyam wrote:
> Hi,
>
> With release 3.10 shipped [1], it is time to set the dates for release
> 3.11 (and subsequently 4.0).
>
> This mail has the following sections, so please read or revisit as needed,
>   - 3.11 focus areas
>   - Release owners
Focusing on the above 2 sections, in this mail.
> *3.11 focus areas:*
> As maintainers of gluster, we want to harden testing around the various
> gluster features in this release. Towards this the focus area for this
> release are,
>
> 1) Testing improvements in Gluster
>   - Primary focus would be to get automated test cases to determine
> release health, rather than repeating a manual exercise every 3 months
>   - Further, we would also attempt to focus on maturing Glusto[7] for
> this, and other needs (as much as possible)
We are yet to see any testing improvement suggestions for the release, 
request the community to help with the same.

Nigel sent a good mail stating what it means to have a good build that 
can be released, here [8]. Please add to that, or propose your thoughts.

Further, during 3.9 there was an effort to collect per component health 
checks that need to be done for a release by Pranith and Aravinda, if 
component maintainers agree, then these can be targeted for automation 
as well. See [9] (@Pranith, @Aravinda, The etherpad where we collected 
this information is defunct, if you have the information somewhere, 
please post a new link for the same).

Also, we would like github issues for these testing improvements, so 
that we can track them for the 3.11 and further release, to ensure we 
reach this goal at some point in the future.
> - We will still retain features that slipped 3.10 and hence were moved
> to 3.11 (see [4] for the list).
Are there other features that are being targeted for 3.11? If so please 
post the same to github and also send a mail to devel and users, stating 
what they are.

We would like to hear sooner, than later about what *may* get into 3.11
> *Release owners:*
>   - Primary: Shyam <srangana at redhat.com>
Assisted by: Kaushal <kmadappa at redhat.com>

Kaushal has volunteered to assist me with this release going forward, 
thanks Kaushal. So now that is 2 people you can post your queries to (in 
addition to the lists), about the release.
>
> Shyam
>
> [1] 3.10 release announcement:
> http://lists.gluster.org/pipermail/gluster-devel/2017-February/052188.html
>
> [2] Gluster release schedule:
> https://www.gluster.org/community/release-schedule/
>
> [3] Mail regarding facebook patches:
> http://lists.gluster.org/pipermail/gluster-devel/2016-December/051784.html
>
> [4] Release scope: https://github.com/gluster/glusterfs/projects/1
>
> [5] glusterfs github issues: https://github.com/gluster/glusterfs/issues
>
> [6] github issues for features and major fixes:
> https://hackmd.io/s/BkgH8sdtg#
>
> [7] Glusto tests: https://github.com/gluster/glusto-tests
[8] Good build thread: 
http://lists.gluster.org/pipermail/gluster-devel/2017-March/052245.html

[9] Release checklist of tests collected during 3.9: 
https://public.pad.fsfe.org/p/gluster-component-release-checklist
NOTE: The above link is defunct now, hopefully we still have the data 
and we can post it again elsewhere

On 02/28/2017 10:17 AM, Shyam wrote:
> Hi,
>
> With release 3.10 shipped [1], it is time to set the dates for release
> 3.11 (and subsequently 4.0).
>
> This mail has the following sections, so please read or revisit as needed,
>   - Release 3.11 dates (the schedule)
>   - 3.11 focus areas
Pinging the list on the above 2 items.
> *Release 3.11 dates:*
> Based on our release schedule [2], 3.11 would be 3 months from the 3.10
> release and would be a Short Term Maintenance (STM) release.
>
> This puts 3.11 schedule as (working from the release date backwards):
> - Release: May 30th, 2017
> - Branching: April 27th, 2017
Branching is about 2 weeks away, other than the initial set of overflow 
features from 3.10 nothing else has been raised on the lists and in 
github as requests for 3.11.

So, a reminder to folks who are working on features, to raise the 
relevant github issue for the same, and post it to devel list for 
consideration in 3.11 (also this helps tracking and ensuring we are 
waiting for the right things at the time of branching).
>
> *3.11 focus areas:*
> As maintainers of gluster, we want to harden testing around the various
> gluster features in this release. Towards this the focus area for this
> release are,
>
> 1) Testing improvements in Gluster
>   - Primary focus would be to get automated test cases to determine
> release health, rather than repeating a manual exercise every 3 months
>   - Further, we would also attempt to focus on maturing Glusto[7] for
> this, and other needs (as much as possible)
>
> 2) Merge all (or as much as possible) Facebook patches into master, and
> hence into release 3.11
>   - Facebook has (as announced earlier [3]) started posting their
> patches mainline, and this needs some attention to make it into master
>
Further to the above, we are also considering the following features for 
this release, request feature owners to let us know if these are 
actively being worked on and if these will make the branching dates. 
(calling out folks that I think are the current feature owners for the same)

1) Halo - Initial Cut (@pranith)
2) IPv6 support (@kaushal)
3) Negative lookup (@poornima)
4) Parallel Readdirp - More changes to default settings. (@poornima, @du)
> [1] 3.10 release announcement:
> http://lists.gluster.org/pipermail/gluster-devel/2017-February/052188.html
>
> [2] Gluster release schedule:
> https://www.gluster.org/community/release-schedule/
>
> [3] Mail regarding facebook patches:
> http://lists.gluster.org/pipermail/gluster-devel/2016-December/051784.html
>
> [4] Release scope: https://github.com/gluster/glusterfs/projects/1
>
> [5] glusterfs github issues: https://github.com/gluster/glusterfs/issues
>
> [6] github issues for features and major fixes:
> https://hackmd.io/s/BkgH8sdtg#
>
> [7] Glusto tests: https://github.com/gluster/glusto-tests
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel