I have a problem with translation files. Normally I add the translation file to the selected branch, like I add the 6.x-2.0 translation to the DRUPAL-6--2 branch. So if you continue to work in the DRUPAL-6--2 branch and create the 6.x-2.1 release then the translation file will be packed with the release.
But as I see your release process is different. You work in the HEAD branch and create a new branch every time when you want to create a new release and number it like 1.0, 2.0, 3.0, therefore the translation file never gets into the actual release.

Normally I could commit the translation file into the HEAD, and then it will be packed. But this is a different process than I use with other modules, I need to commit the translations into two branches and also need to check if you are not using the HEAD branch for something else..
I only have to add the translation file into HEAD when the module developer uses HEAD branch for the new releases, for example views module (for now) uses the HEAD branch for views-6.x-2.x http://drupal.org/node/95897, and there is no 6--2 branch..

So I would expect that if you have a 6--2 branch for the corner-6.x-2.x releases (http://drupal.org/node/354746) then you commit the new changes into that branch and also use the second number (patch level) for the release, like 2.1.
That would make my and other translators life easier.

Comments

kirie’s picture

kirie commented

Hello Pasqualle,

The reason I created a new main release this time around was that there were a bunch of new features - so incrementing the module to 6.x-1.1 didn't seem appropriate. So generally, if there was a bug-fix release I would have fixed it in the branch and created a new release (i.e. 6.x-1.1). All new features go into HEAD until its time to create an actual release, at which point I create a branch and edit the 6.x-2.x-dev (http://drupal.org/node/354746) release node to point to the new branch instead of HEAD. I'm still new to how to best organize releases of modules in the repository though - so all feedback is welcome :) Maybe I should have released the 6.x-2.0 from HEAD instead?

Back to your issue - if you commit the translation to the DRUPAL-6--2 branch I can create a new release (6.x-2.1) which includes that. If you also commit it to HEAD it would be included in any future releases.

Thanks!

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Status: Active » Fixed

You should not create a new release just for one new translation, because your users will be pissed if they have to update just for a translation which they do not need..

Ok, I think then there is no issue. Your repository is well organized. It was just a wrong time, wrong place scenario.
But maybe another advice, the 3.x release cycle should start with alpha, beta or rc release. It is not a good practice to start with a stable release no matter how stable the code is..
Thanks kirie.

Status: Fixed » Closed (fixed)

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