Task #1587
closedTask #1560: Testing of the product (9.5.0)
2 pull requests pending (language edit) since Feb 22
100%
Description
https://github.com/bcvsolutions/CzechIdMng/pulls
Can you merge these please?
I would like to continue editing, I already have a further list of notes.
Generally, when's the best time to make language changes - and merge them with releases?
Files
Updated by Ondřej Kopr over 5 years ago
- File 001.png 001.png added
- File 002.png 002.png added
- File commit.png commit.png added
- Status changed from New to Needs feedback
- Assignee changed from Ondřej Kopr to milus kotisova
- https://github.com/bcvsolutions/CzechIdMng/commit/5803e35890bdc3260280707426921104e3f514f2
- https://github.com/bcvsolutions/CzechIdMng/commit/7497ccb5641ecdd813cdd1c8b9504427652778ae
This way how to notify someone that he must made for me some work is not nice. Please don't create these tickets, you can use slack or mobile for check in which status is some work.
Otherwise we all look at your changes before. The changes that you did isn't probably what you really want. For example:
- You want probably edited localization in password change form (after login), but you didn't edit anything on this detail:
- you edited the public password change and now localization message are very different in cz/en:
Did you try your changes? Someone must now check all places :( that you edit and check if it correct in both languages and this is really boring and long work and now we all have different more priority work. But :) you can continue with correction, it is not required to wait for these changes, or not?
For future speed up you can edit more files in one branch and send it at the once.
Updated by Radek Tomiška over 5 years ago
- Status changed from Needs feedback to Closed
- Target version set to Quartz (9.6.0)
- % Done changed from 0 to 100
Vitek removed part of changes with issues above and I merged both branches into develop.
Thx for this localization improvements.
Updated by milus kotisova over 5 years ago
Thank YOU.
And sorry about the extra pain.
From now on, I will always create a ticket beforehand, then add the number of the ticket in the commit with a short description, and pass it on.