VIVO-1890: Document i18n features in sprint

[chenejac]

Andrew Woods (Migrated from VIVO-1890) said:

This task is to document a full list of the features that are included in the i18n sprint updates.

 

The included file contains the list of modified files with the line number and the message preview.

The command that generated this file is:

 

find VIVO* Vitro* -type f -exec grep -Hn UQAM {} \; 

Each UQAM message is categorized according to the following classification:

The change affects all file types. That's why there are no limitations to java in the search for

 

-Add-Feature

-Optimization -Linguistic-Management -Bug-Correction

[chenejac]

Michel Héon said:

[~accountid:60785ded115da6006f540529] see comment in ticker description

[chenejac]

Michel Héon said:

[~accountid:60785ded115da6006f540529]

As indicated, each modification belongs to a category. Some of them concern bugs or features that don't belong to the i18n itself. In addition, some changes are distributed in multiple files. Here is what I suggest to do.

1- I can group modifications by subject.

2- For each subject, I create a Jira ticket indicating the list of files concerned.

3- For each ticket, create a GIT branch, then make the necessary tests on the concerned files and once modified, send a pull request. We take this opportunity to remove the UQAM comment in the files.

This process will allow to better segment, analyze, manage the modifications and the integration in master, since they will be processed by piece. Especially for cases that are not related to internationalization but more to bug fixes and non-i18n features.

 

[chenejac]

Andrew Woods said:

Thanks [~accountid:5d7a3f78458a170db4b08b25]. Your proposal sounds like a great plan for categorizing the updates in the i18n branches, testing those updates, and removing UQAM comments in the process.

The intent of this ticket is to document (likely in the wiki), the list of features/changes that the VIVO community can read in order to have a clearer understanding of what can be expected from the current i18n effort.

Are you thinking that the wiki documentation (the focus of this ticket) will come in the process of the testing proposal you are suggesting, or in some other way?

[chenejac]

Michel Héon said:

No problem [~accountid:60785ded115da6006f540529] I will do-it today. Is it possible to tell me where in the WIKI this documentation should be done?

[chenejac]

Andrew Woods said:

Could you please start by creating a child page of: https://wiki.lyrasis.org/display/VIVO/Sprint+-+i18n+Editing

..and we can move it to a different location once the effort has been merged into the master branch(es).

[chenejac]

Michel Héon said:

[~accountid:60785ded115da6006f540529]

Java Corrections classification list is available at [https://wiki.lyrasis.org/display/VIVO/i18n+Update+list+to+be+merge+to+master]

 

[chenejac]

Andrew Woods said:

Nice