Modify

Opened 4 years ago

Closed 4 years ago

#7517 closed task (fixed)

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

Reported by: hasienda Owned by: hasienda
Priority: normal Component: DataSaverPlugin
Severity: normal Keywords: i18n l10n
Cc: Trac Release: 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.

Attachments (0)

Change History (4)

comment:1 Changed 4 years ago by hasienda

  • Summary changed from Start a 0.12 branch, i.e. for i18n of this plugin to [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 4 years ago by hasienda

  • Owner changed from rharkins to hasienda

Taking over responsibility after plugin adoption.

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

comment:3 Changed 4 years ago by hasienda

(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 4 years ago by hasienda

  • Resolution set to fixed
  • Status changed from new to closed
  • Summary changed from [patch] Start a 0.12 branch, i.e. for i18n of this plugin to 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.

Replying to hasienda:

![...]
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.

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from hasienda. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.