Closed cessda-bitbucket-importer closed 2 years ago
Original comment by Taina Jääskeläinen.
Thanks, Martin. Everything else is OK but one small issue:
I’m translating a new version of SL into TL with some non-SL induced changes as well, and am changing the TL status to ‘Ready to be published’. The TL pop-up:
I left the change log info open to demonstrate what it was.
‘Code added’ is copied to ‘Version changes’ but the change log information not. (Note: there is a same change done twice, i.e. a duplicate notation, but it the responsibility of the TL to drop one of them from Version changes).
BTW: The TL should not be able to edit the version number in this TL pop-up anymore but maybe it is easier to change this alongside with the versioning changes.
Original comment by Taina Jääskeläinen.
@pakoselo Will this remain assigned to you or will I assign it to Stefan?
Original comment by Taina Jääskeläinen.
On further testing, noted that the actually the change log:
Original comment by Taina Jääskeläinen.
@Stifo Should I assign this to you?
Original comment by Stefan Dlugolinsky (GitHub: Stifo).
this works in Chrome browser, but does not work in Firefox, duplicate of #423, will solve this there
Original comment by Taina Jääskeläinen.
The issue with Firefox be solved in #423, so putting this as duplicate.
Original comment by Taina Jääskeläinen.
Duplicate of #423.
Original report on BitBucket by Taina Jääskeläinen.
Language-specific version history for TLs is produced at the time the TL admins clicks on ‘Ready to be published’.
If the language content for that vocabulary has been published previously, TL admins get a pop-up where they have :
Change log
Basically this is the same pop-up that the TLs have now at the time when they change the status to Published, except that the version number is non-editable and ‘code deleted’ is now ‘code deprecated’.