Ian Bicking <[EMAIL PROTECTED]> writes:
> I'm wondering how the releases should work. An update to a translation
> doesn't really warrant a new software release, and releases of
> FormEncode are otherwise going to be uncommon. Should the translations
> be shipped as separate packages (e.g., formencode.lang.de)? It's
> potentially a lot of packages, but that might be fine. They can be
> released and updated on their own schedule then. Does that sound feasible?
If there aren't that many changes to messages -- i.e., FormEncode's code
should change more than its messages --, then I don't see a reason for
separating things.
Once translations stabilize then it would be easy to update them for a new
release.
What I imagine for cases like this:
- bump version (e.g. from 0.5 to 0.6 to signal the great changes)
- keep all translations and code together
- after initial release with some translations release a new minor
version once in a while to include new languages
This is so because one will be able to tell what he has available just from
FE's version. Lets say that 0.6 included en, de and pt_BR. When 0.6.1 comes
out we'll know that it adds es and zh_CN, for example.
If we get all languages included by 0.6.5 (for example), then we'll only have
to make a new release due to I18N if:
- there was some gross mistake in a translation
- there were messages added (hence new FE code)
We could also make a formencode.i18n package exclusive to translations.
The way things works all what is needed is a new potfile to enable a new
langauge, no code changes after initial setup.
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
