[SOLVED] How to release new version of module?

[Sonya]

Hello,

stupid question probably answered here but not found.

I have found a module that I would like to update and release a new version. I have contacted the author of the module and he has added me to the developer list. Now what? I can not see the possibility to add new release, as I normally have with my own modules. Where can I create a new release and upload files?

Please help  ::)

Sonya

[alby]

Now what? I can not see the possibility to add new release, as I normally have with my own modules. Where can I create a new release and upload files?

Sorry, admin only can add a new release

Alby

[Sonya]

Sorry, admin only can add a new release

Thank you for reply. One question more: what is the purpose to be added to the developer list of the module in this case except of be listed to the right?

[alby]

what is the purpose to be added to the developer list of the module in this case except of be listed to the right?

Sorry, I don't understand what you say

Alby

[Sonya]

Sorry, I don't understand what you say

Sorry  I mean, when I am added to the developer list of the module, I can see my name in the section "Developers" to the right. What else? Bugs can be assigned to my name. Are there any other features that I have additionally to "normal", non-developer user status?

And how is the process of release is defined now? Must I send files with my changes to the admin of module. Or can I submit them in SVN (I have not ever worked with SVN)?

I know: a lot of questions. But I would like to understand how developers can collaborate in most efficient way.

Thank you for your patience 

[alby]

Or can I submit them in SVN (I have not ever worked with SVN)?

yes
Difference from admin and develop are that admin has control on "file release" and request user join
For coding/bug/Feature request is same

Alby

[Sonya]

yes
Difference from admin and develop are that admin has control on "file release" and request user join
For coding/bug/Feature request is same

Thank you again. I have committed my changes to SVN.

Last question: What about translation files? I have to change en_US file to update help. Should I do it in SVN or with translation center (I do not not have access to translation center except of Russian)? Or must I change the file lang/en_US.php directly?

EDIT: I have found this topic http://forum.cmsmadesimple.org/index.ph ... 639.0.html

As I understand the natural language file must be changed via svn:

Please do not commit any language file other than the one for your module’s natural language (actually the natural language of the module as listed in the Forge categorisation)

Where can I find forge categorisation? As this is not my module, I am not sure what language is the "natural one" for it.

[alby]

Or must I change the file lang/en_US.php directly?

yes, language file in lang folder is primary language, translation languages come in ext subfolder automaticaly

Alby