Upcoming SubtitleComposer 0.7.1 release / string freeze

[Mladen Milinkovic]

Actually I would prefer to just tag releases in master branch, at least until project reaches version 1.0.

I thought that the release branch was requirement, if it's not will just drop release/0.7 branch.

Should I modify i18n.json in repo-metadata to contain following:
|{"trunk":"none","stable":"none","stable_kf5":"|||master|","trunk_kf5":"master"}|
right now it's:
|{"trunk":"none","stable":"none","stable_kf5":"none","trunk_kf5":"master"}|

Also I should modify logical-module-structure in repo-metadate and change release/0.7 to master.

Is that correct?

Grazie

On 7/28/21 9:06 PM, Luigi Toscano wrote:
> Mladen Milinkovic ha scritto:
>> Hi all,
>>
>> SubtitleComposer team is polishing the latest changes and preparing
>> for the next release. A string freeze is in effect from now.
>>
>> Since this is first release since moving to KDE infrastructure am
>> not sure whether translations need to be branched and repo-metadata
>> updated. Release branch is "release/0.7".
>>
> Hi,
> thanks for the notice.
> If you plan to keep releasing bugfix releases from that branch, then it should
> be marked as the stable i18n branch in repo-metadata and we need to copy the
> translations to that branch.
> If subsequent bugfix releases are going to be tagged from master then no need
> (but I guess in that case you wouldn't have created that branch).
>
> Ciao

-- 
Mladen Milinkovic
GPG/PGP: EF9D9B26