Agreed. Let's push it out and bake in the doc process for the next release.
Justin - you are in charge of defining the release requirements for the
follow-up docs release.
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.
On Apr 15, 2014 5:36 PM, Justin Clift jus...@gluster.org wrote:
On 15/04/2014, at 10:02 PM, John Mark Walker wrote:
Justin - you are in charge of defining the release requirements for the
follow-up docs release.
No. I'd rather not be.
Ok. Someone will need to step up.
Can we
On Apr 15, 2014 6:09 PM, Jeff Darcy jda...@redhat.com wrote:
It's a developer problem *and* a user problem either way.
Right. The most productive thing we can do right now is come up with a plan for
future releases.
Because the expectations for docs were not set until the last minute, it's
Like I always say, I'm just a user. I'm happy when my input is considered but
I'm not a developer so I know that my -1 doesn't really count.
I'm kind of surprised it's this hard and that in the week this has been
discussed as a release requirement that it didn't just get done. Now we're
saying
Please get the documentation done.
+1 on that. It shouldn't even need to wait for a release. It shouldn't even
have to wait for people to agonize over the wording, or fight with
Markdown/AsciiDoc/whatever. Justin's a great communicator. So's Joe.
Developers, explain what you've done to one of
On Thu, Apr 10, 2014 at 11:47:08PM +0530, Lalatendu Mohanty wrote:
On 04/10/2014 11:20 PM, Justin Clift wrote:
Note, the docs go in the /doc directory in the git repo, both 3.5 and
master branches. ;)
When submitting patches to gerrit, feel free to reuse the bug-
branch that was used
Thank you, guys, for taking this on. The community will greatly benefit from
this effort.
-JM
- Original Message -
On Thu, Apr 10, 2014 at 11:47:08PM +0530, Lalatendu Mohanty wrote:
On 04/10/2014 11:20 PM, Justin Clift wrote:
Note, the docs go in the /doc directory in the git
