Open Stack

"Akihiro Motoki" <amotoki at gmail.com> wrote:
> AFAIK, only OpenStack project administrator can create a new Transifex
> project like horizon_havana.
> Daisy or Tom can do that.
> Once a new project is created, a project administrator can configure
> the setting to
> track GitHub repository automatically.
> 
> On Horizon side, we don't have any automated mechanism to update POT
> files in stable/havana,
> so it seems better to update the POT files when cherry-picking a patch
> with string update.
> If so, transifex will be synced automatically after a backport patch is
> merged.

Thanks Akihiro, let's try this. Since Transifex is staying for a bit longer
we really should see about how to enable the automatic jobs for Horizon too.
Maybe we could also make it work for the stable branch then :-)

I read the notes of last night's meeting [0] and saw that there's an
agreement to do a translation update for Havana, great! The stable release
schedule is  available at [1], the first one is planned for Dec 12th. Since
the stable branch freezes one week before the release, any translation update
patch should be completed and proposed to Gerrit before December 5th.

Kind regards,

Julie

[0] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2013/openstack_i18n_meeting.2013-11-21-00.00.log.html
[1] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fhavana_releases

> 
> Regards,
> Akihiro
> 
> 
> On Mon, Nov 18, 2013 at 6:20 PM, Julie Pichon <jpichon at redhat.com> wrote:
> > "Akihiro Motoki" <amotoki at gmail.com> wrote:
> >> On Fri, Nov 15, 2013 at 7:59 PM, Łukasz Jernaś <deejay1 at srem.org> wrote:
> >> > On Thu, Nov 14, 2013 at 6:42 PM, Akihiro Motoki <amotoki at gmail.com>
> >> > wrote:
> >> >> I would like to follow the community decision when we switch Transifex
> >> >> strings to Icehouse.
> >> >> IMO it is better  we keep Transifex Horizon strings for Havana until
> >> >> the next Havana
> >> >> update (2013.2.1) at least and then switch them to Icehouse.
> >> >> I can volunteer to keep Transifex Horizon up-to-date for Havana.
> >> >
> >> > Can't we just rename the Horizon resource as Horizon_havana and open
> >> > the main resource to the master branch? That way the people who want
> >> > to can use transifex to review strings incoming into master (for evil
> >> > strings ;) and do some minor translation work (acknowledging that they
> >> > may be gone with another update) and also we could work separately on
> >> > the current stable branch.
> >>
> >> I think it is a good idea and possible.
> >> Maintaining the development release and the latest stable release
> >> sounds good to me.
> >
> > That sounds great to me as well. Could we also have the stable translations
> > repository track the stable/havana branch? Ideally we would keep string
> > changes to a minimum, but when fixes get in to change something that's
> > obviously wrong (e.g. [0]) I think it would be nice to also have these
> > in stable. Thoughts?
> >
> > Julie
> >
> > [0]
> > https://github.com/openstack/horizon/commit/0314d54391775f09b35759a650dbae2e2ba567aa
> >
> >>
> >> Thanks,
> >> Akihiro Motoki
> >>
> >> >
> >> > Regards,
> >> > --
> >> > Łukasz [DeeJay1] Jernaś
> >> >
> >> > _______________________________________________
> >> > Openstack-i18n mailing list
> >> > Openstack-i18n at lists.openstack.org
> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
> >>
> >> _______________________________________________
> >> Openstack-i18n mailing list
> >> Openstack-i18n at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
> >>
>