[Gluster-Maintainers] Release 4.0: Schedule and scope clarity (responses needed)
atumball at redhat.com
Tue Nov 28 05:05:13 UTC 2017
On Tue, Nov 28, 2017 at 12:57 AM, Vijay Bellur <vbellur at redhat.com> wrote:
> Top posting here.
> I would like to propose that all new features for 4.x have tests in glusto
> and that one successful run of those tests as a necessary condition for the
> release to happen. This effort would help us catch regressions that happen
> in multi node setups and also prevent accrual of further technical debt
> with respect to testing.
I understand the intent here, and would be very ideal for us as a project
if we achieve it.
Two concerns I have to make it a necessary condition to release (or some
* Do we (as developers) aware of glusto framework and how to write tests at
this time ? If not, this activity itself may take some time, and we are
sure to miss the deadline.
* Is the glusto framework ready to get contributions?
- I may be naive in asking it, but how easy is it to add a new feature
into it? specially something like GD2 (which is a core part of Gluster
4.0), or a feature like reflink which touches most of components, but is
technically just 1 of the 50 fops we have?
Also we did ask this question or suggestion to have 'line coverage' report
with you new component along with the feature to get the feature called
'supported', and I don't think any one signed-off on that.
Here is what I am thinking:
* Add as much as possible feature to 4.0, start with marking every one of
them as 'experimental'.
* Move them out of 'experimental' bucket once the test cases are added.
* Aim to get most of these features out of 'experimental' by adding more
test cases before release of 4.1/4.2 (which ever is going to be our LTM
This way, we get to keep the 4.0 release promise (both on features and
timeline), and by our LTM, we can say which of it is 'recommended', and
which is not.
> On Mon, Nov 20, 2017 at 1:04 PM, Shyam Ranganathan <srangana at redhat.com>
>> As this is a longish mail, there are a few asks below, that I request
>> folks to focus and answer.
>> 4.0 is a STM release (Short Term Maintenance), further, 4.1 is also
>> slated as a STM release (although the web pages read differently and will
>> be corrected shortly). Finally 4.2 would be the first LTM (Long Term ...)
>> in the 4.x release line for Gluster.
>> * Schedule *
>> The above also considers that 4.0 will release 2 months from 3.13, which
>> puts 4.0 branching (also read as feature freeze deadline) around
>> mid-December (4 weeks from now).
>> 4.0/1/2 release calendar hence looks as follows,
>> - Release 4.0: (STM)
>> - Feature freeze/branching: mid-December
>> - Release date: Jan, 31st 2018
>> - Release 4.1: (STM)
>> - Feature freeze/branching: mid-March
>> - Release date: Apr, 30th 2018
>> - Release 4.2: (LTM, release 3.10 EOL'd)
>> - Feature freeze/branching: mid-June
>> - Release date: Jul, 31st 2018
>> * Scope *
>> The main focus in 4.0 is landing GlusterD2, and all efforts towards this
>> take priority.
>> Further big features in 4.0 are around GFProxy, protocol layer changes,
>> monitoring and usability changes, FUSE catchup, +1 scaling.
>> Also, some code cleanup/debt areas are in focus.
>> Now, glusterfs/github  reads ~50 issues as being targets in 4.0, and
>> among this about 2-4 are marked closed (or done).
>> Ask1: Request each of you to go through the issue list and coordinate
>> with a maintainer, to either mark an issues milestone correctly (i.e retain
>> it in 4.0 or move it out) and also leave a comment on the issue about its
>> Ask 2: If there are issues that you are working on and are not marked
>> against the 4.0 milestone, please do the needful for the same.
>> Ask 3: Please mail the devel list, on features that are making it to 4.0,
>> so that the project board can be rightly populated with the issue.
>> Ask 4: If the 4.0 branching date was extended by another 4 weeks, would
>> that enable you to finish additional features that are already marked for
>> 4.0? This helps us move the needle on branching to help land the right set
>> of features.
>> maintainers mailing list
>> maintainers at gluster.org
> maintainers mailing list
> maintainers at gluster.org
Amar Tumballi (amarts)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the maintainers