<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jun 21, 2014 at 2:32 PM, Gauvain Pocentek <span dir="ltr"><<a href="mailto:gauvain.pocentek@objectif-libre.com" target="_blank">gauvain.pocentek@objectif-libre.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Le 2014-06-20 14:37, Anne Gentle a écrit :<div class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Tom's patch is fine, let's see if that causes any rage. <br>
<br>
How about this: for the install guide we just don't publish to /trunk. <br>
<br>
I also like the django header but when I suggested using our existing<br>
DRAFT watermark in the 1191447 but someone (can't recall who) said it<br>
wouldn't be enough. <br>
<br>
The /trunk content was meant to be much less findable but over the<br>
years it has become sought. It's probably time to delete it entirely<br>
now that we have docs-draft links always available.<br>
What do you think?<br>
</blockquote>
<br></div>
Could we imagine having a "hidden" build somewhere? It's nice to have the trunk available to check if bugs reported on icehouse have been fixed in the trunk.<br>
<br></blockquote><div><br></div><div>I like this idea and have tried to have /trunk be unsearchable. If we switch /icehouse to be /icehouse and /current and then create a /dev, and never point to /dev links, could it be hidden?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If it's too complicated or even not possible, then I think it's better to drop trunk/.<br>
<br>
Thanks,<br>
Gauvain<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Anne<br>
<br>
On Fri, Jun 20, 2014 at 2:44 AM, Gauvain Pocentek<br>
<<a href="mailto:gauvain.pocentek@objectif-libre.com" target="_blank">gauvain.pocentek@objectif-<u></u>libre.com</a>> wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Le 2014-06-20 09:18, Tom Fifield a écrit :<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
On 20/06/14 15:13, Gauvain Pocentek wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
We've received several bug reports about the auth_strategy nova option<br>
missing from our install procedure these last few days. These bugs are<br>
reported against the trunk doc, by people installing icehouse. The doc<br>
is in fact correct, both in trunk (the default for this option in juno<br>
has changed and we don't need to set it anymore), and in the icehouse<br>
branch (where the option is set up in the procedure).<br>
<br>
Would it be possible to mark the pages in the trunk/ subdirectory of<br>
</div><a href="http://docs.o.org" target="_blank">docs.o.org</a> [1] as "in progress" or "unstable", or anything that would<div class=""><br>
explicitly tell the user that he might not be reading the correct page?<br>
We already have "juno" in the install-guide and config-ref titles, but I<br>
don't think it's visible enough.<br>
</div></blockquote><div class="">
<br>
This is indeed a problem.<br>
<br>
I find it's quite similar to our Critical bug "Clearly mark outdated<br></div>
doc pages" <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1191447" target="_blank">https://bugs.launchpad.net/<u></u>openstack-manuals/+bug/1191447</a> [2]<br>
<br>
I've proposed a patch @ <a href="https://review.openstack.org/#/c/101428/" target="_blank">https://review.openstack.org/#<u></u>/c/101428/</a> [3] that<div class=""><br>
will make it more obvious that trunk is juno, but I don't think it<br>
solves the problem.<br>
</div></blockquote><div class="">
<br>
Users following the guide will very soon realize that this is not what they want with this patch. IMO that's a good thing. With the current trunk/, I'm quite sure that people end up thinking "the doc is not good, I can't get this thing to work". We really don't want them to think that :)<br>
<br></div>
When starting this thread I had the django documentation website in head. They have a relatively visible warning on the top of dev version pages: <a href="https://docs.djangoproject.com/en/dev/" target="_blank">https://docs.djangoproject.<u></u>com/en/dev/</a> [4] . If Tom's patch is not enough, we could look into implementing a similar feature.<div class="">
<br>
<br>
Gauvain<br>
<br>
______________________________<u></u>_________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.<u></u>openstack.org</a><br>
</div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a> [5]<br>
</blockquote>
<br>
<br>
<br>
Links:<br>
------<br>
[1] <a href="http://docs.o.org" target="_blank">http://docs.o.org</a><br>
[2] <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1191447" target="_blank">https://bugs.launchpad.net/<u></u>openstack-manuals/+bug/1191447</a><br>
[3] <a href="https://review.openstack.org/#/c/101428/" target="_blank">https://review.openstack.org/#<u></u>/c/101428/</a><br>
[4] <a href="https://docs.djangoproject.com/en/dev/" target="_blank">https://docs.djangoproject.<u></u>com/en/dev/</a><br>
[5] <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-docs</a><br>
</blockquote>
</blockquote></div><br></div></div>