Hi, Even I'm interested. Ill be working on this for sure.
Regards,
Pranav
On Fri, Mar 15, 2013 at 7:42 PM, Michael Basnight wrote:
> Of course... I spaced. I'd love to review the doc for this.
>
> Sent from my digital shackles
>
> On Mar 15, 2013, at 5:47 AM, "Anne Gentle" wrote:
>
> Yes, go
Of course... I spaced. I'd love to review the doc for this.
Sent from my digital shackles
On Mar 15, 2013, at 5:47 AM, "Anne Gentle"
mailto:a...@openstack.org>> wrote:
Yes, go ahead. Use the guidelines we have for Doc bug triage. [1]
Hey Bas, a DocImpact would have been ideal on that commit me
Yes, go ahead. Use the guidelines we have for Doc bug triage. [1]
Hey Bas, a DocImpact would have been ideal on that commit message so we
could already have a doc bug logged. [2]
Thanks,
Anne
1.
https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines
2.
https://wiki.opens
Hi Anne,
I'm a newbie in the "documentation area" but, I would like to give an help.
I haven't found any documentations (or open bug) regarding the cinder
multi-backend feature (
https://wiki.openstack.org/wiki/Cinder-multi-backend --
https://review.openstack.org/#/c/21815/ ).
Do you know if thi
Hi all,
You all did great with DocImpact, but now that we're less than a month from
release, the tiny doc team is facing a long list of doc bugs that won't be
done by April 4th, many generated by DocImpact flags.
We typically do a "release" of the docs about a month after the actual
release date,
5 matches
Mail list logo
