Opened 7 years ago

Closed 7 years ago

Start a development branch, i.e. for i18n of this plugin

Reported by: Owned by: Steffen Hoffmann Steffen Hoffmann normal DataSaverPlugin normal i18n l10n 0.12

Description

Trac 0.12 is out. Since this plugin does contribute a navigation item to Trac, it can't integrate well into i18n-aware environments without supporting translations itself. I recommend to have a dedicated branch for this development.

Raise your voice, if you see much more benefit from doing a hybrid 0.11/0.12 version, that would have i18n just as an option. I've done this before, but this certainly requires more work for both development and testing at every stage of the life cycle. So please be reasonable with requests, in case you're not able/willing to contribute.

comment:1 Changed 7 years ago by Steffen Hoffmann

Summary: Start a 0.12 branch, i.e. for i18n of this plugin → [patch] Start a 0.12 branch, i.e. for i18n of this plugin

I've already done the patches required to create a dedicated 0.12 branch with full i18n support. It's only a matter of reaching an agreement on details and who could push it into the repository.

comment:2 Changed 7 years ago by Steffen Hoffmann

Owner: changed from Rich Harkins to Steffen Hoffmann

Taking over responsibility after plugin adoption.

This will be done next, including creation a trunk branch for further development.

comment:3 Changed 7 years ago by Steffen Hoffmann

(In [8699]) DataSaverPlugin: Add new branch 'trunk', refs #7517.

This has been initiated to start i18n work, but will serve as development place for new features in general.

comment:4 in reply to:  description Changed 7 years ago by Steffen Hoffmann

Resolution: → fixed new → closed [patch] Start a 0.12 branch, i.e. for i18n of this plugin → Start a development branch, i.e. for i18n of this plugin

As we have a development branch now, what is left to be done, is a «official» release to the 0.11 branch.

![...] Raise your voice, if you see much more benefit from doing a hybrid 0.11/0.12 version, that would have i18n just as an option. I've done this before, but this certainly requires more work for both development and testing at every stage of the life cycle. So please be reasonable with requests, in case you're not able/willing to contribute.

Meanwhile it turned out to be not as hard doing i18n work for some other plugins. At the contrary it might even be preferable to not have a dedicated 0.12 branch, as long as a changes between Trac 0.11 and 0.12 are not relevant for the plugin (DataSaverPlugin is a good example AFAIK) or could be taken care of by providing conditional structures inside the plugin code as needed to do equal things for both Trac versions.

To sum up: I'll try to stick to 0.11 branch and just highlight «compatible with 0.12, ...» as long as possible.

Modify Ticket

Change Properties
Action
as closed The owner will remain Steffen Hoffmann.
The resolution will be deleted.