-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 04/10/14 18:12, Akihiro Motoki wrote: > Thanks all for your input. This topic was also discussed in the > I18N team meeting this week. > > All opinions I got so far are same and we seem to have a > consensus. - not to have mo files (compile message catalogs) in our > source git repository. - to provide a quick documentation on how to > generate mo files and deploy them > > > This consensus raises another question. At now Horizon is the only > affected project. Is it better to apply this consensus to Juno > Horizon release or to defer it to Kilo? One concern is that most > distributions have already prepared packages for Kilo, so it might > be better not to change now? I would like to know opinions from > distributors like RDO, Debian, Ubuntu and so on.
I was pointed (kudos to Alan Pevec) to the following update for RDO spec file  that makes it regenerate MO files from source for Juno. So for RDO, it's already handled the way we will probably go forward. : http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/commit/?id=e756a1d0e401707d6d386516eef5c2af8ed5e138 /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJUMn5lAAoJEC5aWaUY1u570KUIAJRuxXcARheAJQB8phFlarHn zzRNA7hA8WPBEVMRZCJjqqLKEeS/XaSN0Ue8XuR8bX4AOKA+Yh9S2X39kEWGquhI Xdb5OqkHXPrBRAAKIdg9sPIa5SfKF9m9vEWSH84nGDczhQTeV6XBJtrnBgL9USa7 bMmifiXg14lSNNgwwpiEkyoA1qmEsMki+yFPuvldWLvszWgl3xlTOZnY1L7auUgU DO9bWuvSa10O463+CH4SbhhwE/k8TS3B5A/Y7eKeFwLECAHQFumgFK3bQtFE7QfB Lv29eonr6NchEtGo+tu1W10ervDAoEVqMF6oLFtg+qF3hJwyumhH9pIV9PXVO5g= =fkXa -----END PGP SIGNATURE----- _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev