On 07/04/2014 08:44 PM, Jeff Darcy wrote:
Given the holiday weekend in US, I feel that it would be appropriate
to move the 3.6 feature freeze date to mid next week so that we can
have more reviews done & address review comments too. We can still
continue to track other milestones as per our release schedule [1].
What do you folks think?
I think the answer depends on what we can expect to change between now
and then. Since the gluster.org feature page never got updated to
reflect the real feature set for 3.6, I took the list from email sent
after the planning meeting.
* Better SSL
Two out of three patches merged, one still in review.
* Data Classification
Design barely begun.
* Heterogeneous Bricks
Patch has CR+1 V+1 but still stalled in review.
* Trash
Ancient one is still there, probably doesn't even work.
There is an improved implementation of trash in gerrit and can help get
more traction with more reviews, rebases etc.
* Disperse
Patches still in very active review.
* Persistent AFR Changelog Xattributes
Patches merged.
* Better Peer Identification
Patch still in review (fails verification).
* Gluster Volume Snapshot
Tons of patches merged, tons more still to come.
* AFRv2
Jammed in long ago.
* Policy Based Split-Brain Resolver (PBSBR)
No patches, feature page still says in design.
* RDMA Improvements
No patches, feature page says work in progress.
Don't think there are any major pieces missing to get rdma functional.
More testing and bug fixes should be mostly it. Can happen in the
interval between feature freeze and code freeze.
* Server-side Barrier Feature
Patches merged.
Update on a few other nice to have features that have either made the
cut or can become available with some effort:
* glusterd volume locks - already in
* better logging - framework & few xlators have adopted this
* Exports Netgroups authentication - Needs some review attention and rebases
* Gluster user serviceable snapshots - feature already in
* rest-api - Early implementation available, need some more reviews
* Object Count & Archipelago - have some code, need a little more effort
to make it available.
That leaves us with a very short list of items that are likely to change
state.
* Better SSL
* Heterogeneous Bricks
* Disperse
* Better Peer Identification
Of those, I think only disperse is likely to benefit from an extension.
The others just need people to step up and finish reviewing them, which
could happen today if there were sufficient will. The real question is
what to do about disperse. Some might argue that it's already complete
enough to go in, so long as its limitations are documented
appropriately. Others might argue that it's still months away from
being usable (especially wrt performance). In a way it doesn't matter,
because either way a few days won't make a difference. We just need to
make a collective decision based on its current state (or close to it).
If we need to wait a few days before people can come together for that,
so be it.
My inclination with respect to disperse/ec is to get it into the code
base and mature it there (mostly from a performance perspective).
Better peer identification, trash and subset of the features in above
lists can benefit by a few days extension. So it seems worthwhile for me
to push out feature freeze till mid next week.
-Vijay
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
