We need to know that we are able to update the translations files for the next release or release an strings freezed version and wait for translations job to be done.

All translators should subscribe here for the next release.

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

I will do it when the release 6.1 will be available.
Anyway, before the definitive release there will be a beta release first; is it fine if the translators will get a notification right then?

hass’s picture

hass commented
Status: Postponed (maintainer needs more info) » Active

The release cycle should be:

1. 6.x-1.x-dev
2. 6.x-1.x-betaX (not required, but good if many changes)
3. 6.x-1.x-rcX (string freeze, only critical bug fixes to strings are allowed)
4. 6.x-1.X final release.

Same logic for D5.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

So, to make a summary, I should advice 72 hours before I commit the first final release (6x-1.0, in this case).

hass’s picture

hass commented

At least 72 hours before you TAG the next new versions.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed (maintainer needs more info) » Active
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Priority: Critical » Normal
hass’s picture

hass commented
Priority: Normal » Critical

It's critical as updated translations it should be required for the final release. Do not release without updated translation packages, please. Critical mark a task that needs to be done first. THX.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Priority: Critical » Normal

That is why I changed the priority; the priority goes to fix the code not to create the translation files which, like you said, can be done after all the code is stable.

hass’s picture

hass commented
Priority: Normal » Critical

For the *newbies* in here - a task or bug that is marked critical - normally BLOCK's a release. That's why it is marked critical to also make clear how important this task is and should make other developers not to skip this task in a distributed project where people do not sit together and see themself in the eyes. Setting status back to the appropriate priority.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Maybe I was not clear in what I meant. I don't need any block, as I remember to notify the translators 72 hours before the first official release.

Talking of newbies, it was not me who didn't know anything about the value returned from db_placefolder(), and asked twice about that.
As I don't give nicks to other people, I would like other people would do the same with me.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Priority: Critical » Normal

I am changing the priority, as the assumption that a task with critical priority would block an official release to be created is not true.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Notify translators at least 72 hours before release. » Notify translators at least 72 hours before an official release
Anonymous’s picture

Anonymous (not verified) commented

Kiam, how close do you think we are at this moment? Will the plan be to create a -beta and give a few days for the translators?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I think the translators should be advised before to create the first official release that is not a beta version.

hass’s picture

hass commented

Only to note that Gabor recommended that all module maintainers should release a "RC" with string freeze for translators... as bigger the projects are and as far the maintainer is away from the translators or do not communicate with them - the more sense this makes. For modules having many changes and 100+ strings it's the best way...

...and we would also do not need to raise this 72 hours issues (what may be a very short timeframe for many strings)

Anonymous’s picture

Anonymous (not verified) commented
Issue tags: +internationalization

Sometimes I need to add a comment to add a tag, why?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

It happens to me as well. Sometimes Drupal.org allows me to change a single data, sometimes it forces me to write a comment; most of the times, anyway, it allows me to change something without to leave a comment.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

See #377596: Adding issue tags without a comment or change in other metadata does not work.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Translators also please read #445004: Notes for who adds the translation files - make sure you are not creating one big .po file. They must be split up per-module.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Component: Other » Translations

Moving to Translations component.

Anonymous’s picture

Anonymous (not verified) commented

All strings are considered frozen for 6.x-1.x-dev. Any changes to strings must pass through #498764: String freeze - June 24th. I plan a RC1 release July 1st.

Anonymous’s picture

Anonymous (not verified) commented

I plan to release the official 6.x-1.0 package sometime after July 7th 16:00 UTC.

hass’s picture

hass commented

Are you planing to release a 5.x-1.7 at the same time? I saw a D5 patch for Bing in #479892: Switch from Live Search to Bing. This may need a few updates to the D5 translation, too.

Anonymous’s picture

Anonymous (not verified) commented

The patch for 5.x-1.x rests untested so no, it will not be released at the same time. I will give you consideration for the translations before I release it.

Anonymous’s picture

Anonymous (not verified) commented

RC2 has been released. Please take note of http://drupal.org/project/issues/search/xmlsitemap?issue_tags=new%20tran... as there is one new string. I plan to make an official release on July 29th.

hass’s picture

hass commented
Status: Active » Fixed

Seems to be fixed for final 6.x-1.0.

Status: Fixed » Closed (fixed)
Issue tags: -internationalization

Automatically closed -- issue fixed for 2 weeks with no activity.

Issue tags: +internationalization

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.