<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello,<br>
<br>
<br>
Matt Kassawara wrote on 10/11/2016 7:56 AM:<br>
</div>
<blockquote
cite="mid:CABA+jQp5GK_q3vWzrEY4-Yv+ztcKM84g1ymgwBuFDiWA4yJhZA@mail.gmail.com"
type="cite">
<div dir="ltr">For a moment, let's assume Newton isn't released
yet because openstack-manuals hasn't branched yet.</div>
</blockquote>
<br>
I have also heard that stable/newton branch will be released around
Barcelona Summit.<br>
I am waiting for new documentation release to create corresponding
stable versions in Zanata (translation platform).<br>
<br>
<blockquote
cite="mid:CABA+jQp5GK_q3vWzrEY4-Yv+ztcKM84g1ymgwBuFDiWA4yJhZA@mail.gmail.com"
type="cite">
<div dir="ltr"> I'm working on some significant beneficial changes
to the networking guide that resolve a number of issues we
probably should have addressed a while ago... ideally before the
release of Mitaka... but I couldn't accomplish it and no one
else contributes to this particular content. The networking
guide isn't continuously published. When my changes to it merge
in master, they are essentially invisible to operators until the
next release. Operators often run a stable release or two behind
master. Thus, only merging in master (which becomes the next
release) limits the audience of the changes. Backporting such
changes to the prior release (if they apply) makes them visible
to a wider audience. Furthermore, this particular patch resolves
a number of issues with the Mitaka content. Finally, doesn't the
same issue of translation apply to continuous-release content
such as the admin guide?</div>
</blockquote>
<div dir="ltr"><br>
I18n team set *install-guide (+common)* and *networking-guide* as
documentation translation targets for Mitaka.<br>
(For Newton, I need to identify targets with discussions later.)<br>
</div>
Since admin-guide translation occurred in master branch and also is
not main translation target, continuous-release in admin-guide is
fine currently to translators.<br>
<br>
<blockquote
cite="mid:CABA+jQp5GK_q3vWzrEY4-Yv+ztcKM84g1ymgwBuFDiWA4yJhZA@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Oct 10, 2016 at 4:22 PM,
Akihiro Motoki <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:amotoki@gmail.com" target="_blank">amotoki@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Correction.<br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">2016-10-11 7:20
GMT+09:00 Akihiro Motoki <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:amotoki@gmail.com" target="_blank">amotoki@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>Does the openstack-manuals project allow
a big refactoring in **stable** branches?</div>
</div>
<div><br>
</div>
I saw a big refactoring on the networking guide
was merged in the master branch
<div>and it was backported into stable/mitaka
branch.</div>
<div><br>
</div>
<div>As a result of the backport, 25% of
Japanese Mitaka Networking Guide translation.<br>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>As a result of the backport, 25% of Japanese
Mitaka Networking Guide translation was lost.</div>
<span class="">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>I was really shocked that such thing
happened in a stable branch.</div>
<div>If the project allows such backport,
translators will easily lose their translation</div>
<div>and it implicitly means the project
suggests not to translate it.</div>
<div><br>
</div>
<div>I would like to know the policy of the docs
stable branch maintenance.</div>
</div>
</blockquote>
</span></div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
+1<br>
<br>
And a sort of notification to translators if lots of changes on
stable branches are going to be applied would be needed..<br>
<br>
<br>
With many thanks,<br>
<br>
/Ian<br>
<br>
<blockquote
cite="mid:CABA+jQp5GK_q3vWzrEY4-Yv+ztcKM84g1ymgwBuFDiWA4yJhZA@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><span class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><span
class="m_2786464896923253493HOEnZb"><font
color="#888888">
<div><br>
</div>
<div>Akihiro</div>
<div><br>
</div>
</font></span></div>
</blockquote>
</span></div>
<br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
OpenStack-docs mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs"
rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-docs</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-I18n mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-I18n@lists.openstack.org">OpenStack-I18n@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>