<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 29, 2013 at 11:28 PM, Tom Fifield <span dir="ltr"><<a href="mailto:fifieldt@unimelb.edu.au" target="_blank">fifieldt@unimelb.edu.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 30/03/13 11:27, Laura Alves wrote:<br>
><br>
><br>
> On Fri, Mar 29, 2013 at 7:47 PM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a><br>
</div><div class="im">> <mailto:<a href="mailto:anne@openstack.org">anne@openstack.org</a>>> wrote:<br>
><br>
> Hi all,<br>
> Would you be okay if we stop using /trunk/ for the current "built<br>
> from git" versions of the documentation and copied the files to<br>
</div>> <a href="http://docs.openstack.org/current" target="_blank">docs.openstack.org/current</a> <<a href="http://docs.openstack.org/current" target="_blank">http://docs.openstack.org/current</a>><br>
<div class="im">> instead? The word "trunk" is leftover from bzr/Launchpad days of yore.<br>
><br>
> The tasks that have to happen for this to occur are:<br>
> - Change all the /trunk/ build jobs in openstack-infra/config to<br>
> /current/<br>
> - Check all the pom.xml files for mentions of trunk<br>
> - Ensure that the sitemap.xml stored on the web server contains<br>
> /current links<br>
> - Ensure comments are turned off for /current just like they are for<br>
> /trunk<br>
> - Change all the openstack-manuals/www/ pages to point to /current<br>
> instead of /trunk<br>
> - Change the Google Custom Search Engine from /trunk to /current (we<br>
> hide /trunk from the CSE searches)<br>
><br>
> Anything else? Warn the mailing list or get further input?<br>
><br>
> If no one objects by next Tuesday, I'll put this on my to-do list<br>
> for next week.<br>
><br>
> Thanks,<br>
> Anne<br>
><br>
> P.S. Note that this rename is similar to cutting a doc release,<br>
> documented here: <a href="https://wiki.openstack.org/wiki/Documentation/Release" target="_blank">https://wiki.openstack.org/wiki/Documentation/Release</a><br>
><br>
> _______________________________________________<br>
> Openstack-docs mailing list<br>
> <a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
</div>> <mailto:<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a>><br>
<div class="im">> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
><br>
><br>
> +1<br>
><br>
> If there is consensus about this, does it sound like a good idea to<br>
> split the tasks?<br>
> I can certainly help with the pom.xml files, since I've got some patches<br>
> in review and some others to submit, I could check for trunk in them.<br>
><br>
> Regards!<br>
> Laura<br>
<br>
</div>One note for consideration (just putting this out there - no strong<br>
feelings):<br>
<br>
>From a user perspective, 'trunk' and 'current' could come across quite<br>
differently. As an Operator, when I see 'trunk' I think "oh, that's<br>
something to do with the code. I'm running a production system, so I'll<br>
ignore that and find the stable release". When I see 'current', I<br>
associate that with the current stable release.<br>
<br>
<br></blockquote><div><br></div><div>This is my thinking as well, that "current" means "current supported version" and not "draft in progress" -- but I've heard otherwise. I think we need a new name for trunk. What about master?<br>
</div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One thing I noticed about the development cycle is that a bunch of<br>
deprecation happened early. Options slated for removal tended to be<br>
deleted as soon as the code freeze was over. I may be living in a dream<br>
world, but I feel that we should be putting these changes into the<br>
documentation as soon as we can after we spot them - an automated system<br>
(which I think is the aim for config options) would certainly do this.<br>
With changes in this manner, the 'current' doc would be quite quickly<br>
inconsistent with 'current stable release' and that could cause confusion.<br>
<br></blockquote><div><br></div><div>Yes we definitely should automate the config files - Tom can you share your process?<br><br></div><div>Anne<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All this can likely be fixed by some careful wording in the release<br>
selection page for those coming via <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a>, but I worry<br>
about those who come in direct via Google. Perhaps a little 'draft' or<br>
'pre-release' banner with a link to the current release is needed in the<br>
template.<br>
<br>
<br>
Thoughts?<br>
<br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div><br></div></div>