March 2024 - OpenStack-I18n - lists.openstack.org

[Bug 1979745] [NEW] Mistype in RU Horizon translation
by Vadym Markov 30 Dec '24

30 Dec '24

Public bug reported: https://translate.openstack.org/webtrans/translate?project=horizon&iteratio… US#view:doc;doc:openstack_dashboard/locale/djangojs;search:Non- Public;textflow:622521 Correct translation is "Образ из другого проекта - непубличный" "л" letter missing ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1979745 Title: Mistype in RU Horizon translation Status in openstack i18n: New Bug description: https://translate.openstack.org/webtrans/translate?project=horizon&iteratio… US#view:doc;doc:openstack_dashboard/locale/djangojs;search:Non- Public;textflow:622521 Correct translation is "Образ из другого проекта - непубличный" "л" letter missing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1979745/+subscriptions

2 1

Survey to schedule i18n SIG 2024.04 PTG
by Seongsoo Cho 19 Mar '24

19 Mar '24

Hi i18n SIG I create a survey to schedule i18n SIG 2024.04 PTG. Please let me know, what time and day works best for you. survey: https://framadate.org/tY49ETqtFD9R4LPt Best Regards Seongsoo -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

1 0

[I18n] IRC Meeting date change on the next week: March 14th, 13:30 UTC
by Ian Y. Choi 07 Mar '24

07 Mar '24

Hello all, Due to schedule changes from active participants, the next I18n meeting will happen on March 14th, 13:30 UTC on #openstack-i18n IRC channel. Note that previous meeting details and logs (2024) are on [1] and [2].. Thank you all, /Ian [1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting [2] https://meetings.opendev.org/meetings/openstack_i18n_meeting/2024/

1 0

[StringFreeze] Soft period was over - Plz contribute translation for the release!
by Ian Y. Choi 07 Mar '24

07 Mar '24

Dear language coordinators & translators! Only a few weeks left before the official 2024.1 Caracal release [1] and I would like to share that the last week was the Soft StringFreeze period. Language teams need to focus on Horizon and Horizon-related projects before all translated strings will be packaged for upcoming release. For more details on how the I18n team is doing with releases (especially Horizon & plugin projects), please see [2]. If you have questions, feel free to ask through openstack-i18n at lists.openstack.org mailing list or ask I18n members on IRC #openstack-i18n channel. Thank you all for your contribution! /Ian [1] https://releases.openstack.org/caracal/schedule.html [2] https://docs.openstack.org/i18n/latest/release_management.html On Fri, Mar 1, 2024 at 11:27 PM Herve Beraud <hberaud(a)redhat.com> wrote: > > Development Focus > ----------------- > > We just passed feature freeze! Until release branches are cut, you > should stop accepting featureful changes to deliverables following the > cycle-with-rc release model, or to libraries. Exceptions should be > discussed on separate threads on the mailing-list, and feature freeze > exceptions approved by the team's PTL. > > Focus should be on finding and fixing release-critical bugs, so that > release candidates and final versions of the 2024.1/Caracal deliverables can be > proposed, well ahead of the final 2024.1/Caracal release date. > > General Information > ------------------- > > We are still finishing up processing a few release requests, but the > 2024.1/Caracal release requirements are now frozen. If new library releases are > needed to fix release-critical bugs in 2024.1/Caracal, you must request a > Requirements Freeze Exception (RFE) from the requirements team before we > can do a new release to avoid having something released in 2024.1/Caracal that > is not actually usable. This is done by posting to the openstack-discuss > mailing list with a subject line similar to: > > [$PROJECT][requirements] RFE requested for $PROJECT_LIB > > Include justification/reasoning for why a RFE is needed for this lib. > If/when the requirements team OKs the post-freeze update, we can then > process a new release. > > A soft String freeze is now in effect, in order to let the I18N team do the > translation work in good conditions. In Horizon and the various dashboard > plugins, you should stop accepting changes that modify user-visible > strings. Exceptions should be discussed on the mailing-list. By > March 25, 2024 this will become a hard string freeze, with no changes > in user-visible strings allowed. > > Actions > ------- > > stable/2024.1 branches should be created soon for all not-already-branched > libraries. You should expect 2-3 changes to be proposed for each: a > .gitreview update, a reno update (skipped for projects not using reno), > and a tox.ini constraints URL update. Please review those in priority > so that the branch can be functional ASAP. > > The Prelude section of reno release notes is rendered as the top level > overview for the release. Any important overall messaging for 2024.1/Caracal > changes should be added there to make sure the consumers of your release > notes see them. > > Upcoming Deadlines & Dates > -------------------------- > > Cycle Highlights Due: March 7th, 2024 (R-4 week) > RC1 deadline: week of March 11, 2024 (R-3 week) > Final RC deadline: week of March 25, 2024 (R-1 week) > Final 2024.1/Caracal release: April 3, 2024 > Dalmatian PTG: April 8-12, 2024 > > -- > Hervé Beraud > Senior Software Engineer at Red Hat > irc: hberaud > https://github.com/4383/ >

1 0