Stages of translations and features

[Y Y]

Dear Team,

This is yang, some of team member may know me, I'm doing translation in community. I've feel unable to achieve the task due to,

say, if one korea company wants to use localized software. then kr.csv was translated. however ,now 

1. Bench update will update code in development branch(not sure if it is good way), which brings new code(new translations need to be done)

2. The new translations need to be done, otherwise, end user feels strange about english words.

In existing way, i feel like if it is only fit for english based country...

any advice...

Thanks,

Yang

[Rushabh Mehta]

Yang, Agreed. What do you suggest?

--
Note:
 
If you are posting an issue,
 
1. ERPNext is a free and open source software and support is given on this forum by a team (https://frappe.io/webnotes). So please consider donating if you find this forum useful (https://frappe.io/buy). Even a small amount would be helpful.
2. We should be able to replicate it at our end. So please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
3. Paste your code at http://pastebin.com or http://gist.github.com and send only the URL via email
4. For sending images, use http://imgur.com or other similar services. Do not send images as attachments. Links are good. Same goes for any file you are going to send.
 
End of Note
---
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to erpnext-developer...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/erpnext-developer-forum/0020665a-3496-4b2c-841f-a39688dd5661%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Y Y]

Dear All,

I'm thinking if need to achieve what I've said, it needs to be planned.

the version number need to used extensively.

1. Daily hotfix release, say currently version number is v4.2, then it need to add extra incremental number, say v4.2.146, each hotfix can be described fixed in which version number

2. Enhancement(minor and major), if minor enhancement won't change resource file(say, language file), then it can be treat as daily hotfix; Major enhancement, it needs to add 2nd incremental number, the version need to be v4.3.0, most important is major enhancement need to planned first other than release it(please don't release it into frappe clould, it will lead user confuse, as it need extra explaination), in addition to that

3. Need to tag stable version, say, v4.2.186 now reaches stable, it need to tagged. I think ERPNext team need to maintain 1 stable version(previous version) and another released version, take an example, v4.2 and v4.3 are 2 stable version, if i'm using v4.1, then official shall provide script to upgrade from v4.1 to v4.3(end user can decide), after upgrade, the IT only need to do is kind of "bench update hotfix" which only bring V4.3's hotfixes into user's site

4. The bench command need to smart enough to update reponsitory if do upgrade(say original is v4.2 tag, now it is v4.3 tag)

Take some real case:

1. V4.2 is stable, it need to be put into tag branch, all hot fixes are againt, say i was in v 4.1, the bench command can easy allow me bench upgrade to v4.2 or only get hotfix for v4.1

If i think v4.1 is good enough, then i will only push hotfix.

if official suggest upgrade to v4.2 then i will setup local test machine first(test new feature and translation if any)

Will this bring benefits?

I think for project management, it is scope management, it will lead team more focus and community more predictable of what will happen next.

Please take a look see if it is reasonable. 

Best Regards,

Yang

在 2014年9月9日星期二UTC+8上午11时50分37秒，Y Y写道：

[Pratik Vyas]

Hi Yang,

From today, we will be
* Release with version numbers
* Version bump will be at least minor if there is change in translation strings.

We think that maintaining two minor release would be too much work.

In the near future, we can have configuration of "pinning". So, if you
pin an app to 4.2, then bench update will update 4.2.45. to 4.2.47,
but will not pull any thing (even hotfixes) from a 4.3 release if
exists.

Thanks,
--
Pratik
ERPNext

[Y Y]

Looking forward to see this.

the "pinning" feature will be great, ones utilize this software will be more free and easy to control the scope.

sure if pin v4.2, it only pin files(hotfixes) relates to v4.3(sure this bug shall also merge into v4.3)

Please help provide feature to upgrade from v4.2 to v4.3, as just like php, version 5.1, version 5.2 those 2 versions upgrade, the IT will take much time test and to consider whether do upgrade.

If the scope of feature is forsee and controlled, I think ERPNext team will have more free time than now:)

Best Regards,

yang

在 2014年9月9日星期二UTC+8下午2时56分13秒，Pratik Vyas写道：