[Gluster-users] Disappointing documentation?

[Jeff Darcy]

On 03/05/2013 04:17 PM, Joe Julian wrote:
> On 03/05/2013 09:33 AM, Shawn Nock wrote:
>> However, since the switch to the new release cycle, bugs don't seem to
>> get fixed (within a release)
> Starting to frustrate me as well. There's too many new features in 3.4 
> for me to feel comfortable making the switch and not enough bugs being 
> backported.

Actually (as the person maintaining the list of fixes which are being
backported to 3.4) it seems like the list is quite extensive.

http://www.gluster.org/glusterfs-3-4-planning/
https://bugzilla.redhat.com/showdependencytree.cgi?id=895528

If anybody has suggestions for other fixes which they'd like to see
backported to 3.4, please *please* let me know.  Direct email will get
my attention fastest, list email will probably work too, comments on
bugs will probably only reach me if they're bugs that I'm already
subscribed to.  I know Joe has already noted done this for a few bugs.
As 3.4 is about to move from alpha to beta, some such requests might not
be fulfilled due to inherent risk of a complicated fix merely replacing
one bug with a new one, but a fix is even less likely to make it into
3.4 if it never gets mentioned or after 3.4 exits beta.  We'll keep
trying to improve this communication in future releases.

BTW, I've greatly enjoyed reading this conversation (and not only
because Shawn said nice things about my articles on hekafs.org *blush*).
 Now is a fantastic time to be bringing this stuff up, because we're all
here in Bangalore right now with the dev summit coming up tomorrow and
Friday.  That means we can get small groups of developers together and
actually do something about some of the ideas that have been discussed.
 I've already made a plan to spend some time on Friday implementing the
idea of providing descriptions for some of the most common or important
error codes.  Some day I'd like to embed this knowledge into a software
agent which watches the logs for the "signatures" of known issues and
boils that information down into concrete and actionable suggestions for
the administrator, but that's more of a long-term thing.  Right now just
having some explanatory text around some of the log messages would be a
help.

Please, keep the ideas coming.  This kind of conversation is extremely
helpful.