No document string freeze on stable branch?
Does the openstack-manuals project allow a big refactoring in **stable** branches? I saw a big refactoring on the networking guide was merged in the master branch and it was backported into stable/mitaka branch. As a result of the backport, 25% of Japanese Mitaka Networking Guide translation. I was really shocked that such thing happened in a stable branch. If the project allows such backport, translators will easily lose their translation and it implicitly means the project suggests not to translate it. I would like to know the policy of the docs stable branch maintenance. Akihiro
Correction. 2016-10-11 7:20 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
Does the openstack-manuals project allow a big refactoring in **stable** branches?
I saw a big refactoring on the networking guide was merged in the master branch and it was backported into stable/mitaka branch.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation was lost.
I was really shocked that such thing happened in a stable branch. If the project allows such backport, translators will easily lose their translation and it implicitly means the project suggests not to translate it.
I would like to know the policy of the docs stable branch maintenance.
Akihiro
For a moment, let's assume Newton isn't released yet because openstack-manuals hasn't branched yet. 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? On Mon, Oct 10, 2016 at 4:22 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
Correction.
2016-10-11 7:20 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
Does the openstack-manuals project allow a big refactoring in **stable** branches?
I saw a big refactoring on the networking guide was merged in the master branch and it was backported into stable/mitaka branch.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation was lost.
I was really shocked that such thing happened in a stable branch. If the project allows such backport, translators will easily lose their translation and it implicitly means the project suggests not to translate it.
I would like to know the policy of the docs stable branch maintenance.
Akihiro
_______________________________________________ OpenStack-docs mailing list OpenStack-docs@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
Hello, Matt Kassawara wrote on 10/11/2016 7:56 AM:
For a moment, let's assume Newton isn't released yet because openstack-manuals hasn't branched yet.
I have also heard that stable/newton branch will be released around Barcelona Summit. I am waiting for new documentation release to create corresponding stable versions in Zanata (translation platform).
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?
I18n team set *install-guide (+common)* and *networking-guide* as documentation translation targets for Mitaka. (For Newton, I need to identify targets with discussions later.) 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.
On Mon, Oct 10, 2016 at 4:22 PM, Akihiro Motoki <amotoki@gmail.com <mailto:amotoki@gmail.com>> wrote:
Correction.
2016-10-11 7:20 GMT+09:00 Akihiro Motoki <amotoki@gmail.com <mailto:amotoki@gmail.com>>:
Does the openstack-manuals project allow a big refactoring in **stable** branches?
I saw a big refactoring on the networking guide was merged in the master branch and it was backported into stable/mitaka branch.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation was lost.
I was really shocked that such thing happened in a stable branch. If the project allows such backport, translators will easily lose their translation and it implicitly means the project suggests not to translate it.
I would like to know the policy of the docs stable branch maintenance.
+1 And a sort of notification to translators if lots of changes on stable branches are going to be applied would be needed.. With many thanks, /Ian
Akihiro
_______________________________________________ OpenStack-docs mailing list OpenStack-docs@lists.openstack.org <mailto:OpenStack-docs@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs>
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On Tue, Oct 11, 2016 at 9:50 AM, Ian Y. Choi <ianyrchoi@gmail.com> wrote:
I have also heard that stable/newton branch will be released around Barcelona Summit. I am waiting for new documentation release to create corresponding stable versions in Zanata (translation platform).
Ian, do you know the when will the infra team working on updating Zanata? --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
Hello Alex! Unfortunately, I have not received updates on updating Zanata. I will check it with Elizabeth and infra team members for status :) With many thanks, /Ian Alex Eng wrote on 10/11/2016 8:59 AM:
On Tue, Oct 11, 2016 at 9:50 AM, Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>> wrote:
I have also heard that stable/newton branch will be released around Barcelona Summit. I am waiting for new documentation release to create corresponding stable versions in Zanata (translation platform).
Ian, do you know the when will the infra team working on updating Zanata?
---------------------------------------------
Alex Eng Senior Software Engineer Globalisation Tools Engineering DID:+61 3514 8262 <callto:+61+3514+8262> Mobile:+614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office:+61 7 3514 8100 <callto:+61+7+3514+8100> Fax:+61 7 3514 8199 <callto:+61+7+3514+8199> Website:www.redhat.com <http://www.redhat.com/>
Hello Alex! I have asked to pleia2, and now Xenial runs on long-lived hosts! Please see http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra... for her plannings. By the way, I have checked that current latest Zanata version is 3.9.5. Can we take it as updating target for translate-dev? Or 3.9.0 is better as we discussed on Austin previously? With many thanks, /Ian Alex Eng wrote on 10/11/2016 8:59 AM:
On Tue, Oct 11, 2016 at 9:50 AM, Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>> wrote:
I have also heard that stable/newton branch will be released around Barcelona Summit. I am waiting for new documentation release to create corresponding stable versions in Zanata (translation platform).
Ian, do you know the when will the infra team working on updating Zanata?
---------------------------------------------
Alex Eng Senior Software Engineer Globalisation Tools Engineering DID:+61 3514 8262 <callto:+61+3514+8262> Mobile:+614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office:+61 7 3514 8100 <callto:+61+7+3514+8100> Fax:+61 7 3514 8199 <callto:+61+7+3514+8199> Website:www.redhat.com <http://www.redhat.com/>
My point is only about stable/mitaka branch of Networking Guide. Honestly I think I am stopping catching up with translation maintenance of Mitaka Networking Guide as I thought only small updates will happen. If we i18n team should assume large changes happen suddenly even for stable branches, perhaps only full-time translators can continue to work on them. The same thing applies to continuously-released guide. For example, Japanese translation of the older admin guide (IIRC some difference name) had good progress, but after the admin guide was refactored drastically, it seems no translators are working on it as it's massive volume and they lost their previous contents. After more than one year passed from the introduction of the new admin guide, Japanese translation percentage is less than 10%. Honestly, the i18n team looks better to revisit documentation translation strategy though I have no good idea. It may be better that the i18n team translates guides with lesser volume to avoid losing a lot.
Japanese team I give up maintaining the translated networking guide. It will be dropped from the Japanese index sooner or later unless someone jumps in. I start to think it is more productive if I add more contents to the upstream guide.
Akihiro 2016-10-11 7:56 GMT+09:00 Matt Kassawara <mkassawara@gmail.com>:
For a moment, let's assume Newton isn't released yet because openstack-manuals hasn't branched yet. 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?
On Mon, Oct 10, 2016 at 4:22 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
Correction.
2016-10-11 7:20 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
Does the openstack-manuals project allow a big refactoring in **stable** branches?
I saw a big refactoring on the networking guide was merged in the master branch and it was backported into stable/mitaka branch.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation.
As a result of the backport, 25% of Japanese Mitaka Networking Guide translation was lost.
I was really shocked that such thing happened in a stable branch. If the project allows such backport, translators will easily lose their translation and it implicitly means the project suggests not to translate it.
I would like to know the policy of the docs stable branch maintenance.
Akihiro
_______________________________________________ OpenStack-docs mailing list OpenStack-docs@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
participants (4)
-
Akihiro Motoki
-
Alex Eng
-
Ian Y. Choi
-
Matt Kassawara