<p dir="ltr">Agreed. Let's push it out and bake in the doc process for the next release.</p>
<p dir="ltr">Justin - you are in charge of defining the release requirements for the follow-up docs release.</p>
<p dir="ltr">Can we agree on this? Let's make this release available by tomorrow so Vijay and I can talk about the just-released 3.5.</p>
<p dir="ltr">-JM</p>
<div class="gmail_quote">On Apr 15, 2014 1:58 PM, "Jeff Darcy" <<a href="mailto:jdarcy@redhat.com">jdarcy@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> Is there _actual pressure_ from a defined source (who I can speak to), or<br>
> is it something such as "we're really overdue already", etc?<br>
<br>
|<br>
That's setting the bar a bit high, don't you think? Those of us at<br>
Summit have all had the dubious pleasure of telling users that the<br>
feature they asked about isn't available in a release yet. Should we<br>
follow up that bad news by asking them to go out of their way to contact<br>
some random guy who's not there, or sign a statement spelling out<br>
exactly what effect lack of that feature had on their decision not to<br>
deploy GlusterFS? Should you provide similar proof regarding your<br>
claims about lack of documentation? Of course not.<br>
<br>
We all get that poor documentation hurts the project. Some of us have<br>
even tried to do something about that. Most of us also realize that<br>
releases dragging on too long *also* hurt the project in a variety of<br>
ways. Having to maintain an active current-release branch in addition<br>
to master is a drag on development. Users are ill served by being<br>
unable to get fixes for actual bugs in easily consumable form. We're<br>
dealing with a tradeoff here, not something where one side gets to put<br>
on a white hat and jam the black hat on somebody else.<br>
<br>
I'm deliberately not taking a position on whether or not we should<br>
release with the documentation in its current state. All I'm saying<br>
is that making inequitable demands of one another, or trying to<br>
portray one another as failing to appreciate users' needs, hurts<br>
the project even more than either poor documentation or late<br>
releases. That's an issue on which I *am* willing to take a stand.<br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a><br>
<a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div>