Akihiro Motoki wrote on 8/10/2017 7:22 PM:
Thanks for taking care.
At now, i18n repo is a part of governance but this is a project which
has no need to cut a release,
so it always follows the master branch of the requirements repo.
It is not a blocker for opening the master branch in the requirements repo.
Right - i18n repository has I18n contributor guide, translation
glossary, and useful scripts with translate.openstack.org
which all do not need to have stable branches to be maintained.
I am not pretty sure but it seems that some project repositories which
are affected by requirements.txt in stable branches
need to follow "stable:follows-policy"  for official projects?
And also thanks a lot - since I also keep on eyes for having stable
branches from translation target repositories in Pike release cycle .
With many thanks,
OpenStack Development Mailing List (not for usage questions)