[openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solum][swift][tacker][tricircle][vitrage][watcher][winstackers][zun] Help needed

Tony Breeds tony at bakeyournoodle.com
Thu Aug 10 22:51:57 UTC 2017

On Fri, Aug 11, 2017 at 12:46:20AM +0900, Ian Y. Choi wrote:
> Akihiro Motoki wrote on 8/10/2017 7:22 PM:
> > Tony,
> > 
> > Thanks for taking care.
> <snip>
> > 
> > > i18n                                               I18n
> > 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.
> > 
> </snip>
> 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.

Now that I know what it is I can handle it in my script.  That's fine
> 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" [1] for official projects?

No that is a seperate thing.  That tag asserts that the code delivered
via that repo adheres to the stable policy.

What this email thread is about is repos that subscribe to the 
Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170811/9a37425d/attachment.sig>

More information about the OpenStack-dev mailing list