Can someone create the Applications/17.08 branches ?

Luigi Toscano luigi.toscano at
Sat Jul 15 23:19:49 UTC 2017

Luigi Toscano ha scritto:
> Albert Astals Cid ha scritto:
>> We have to release the Beta this thursday/friday.
>> I'm going to be AFK for the rest of the weekend, attending a wedding on 
>> monday, a concert on tuesday.
>> So it would be great if someone can create the Applications/17.08 branches 
>> today/tomorrow, (you may need extra karma to be able to create a branch with 
>> that name, ask sysadmins for it if you need it).
> I have to do part of the steps anyway, so I can do it.

Done it, or so I hope.

> Few notes for future reference:
>> What needs to be done (unless i forget something that always can happen) is:
>>  * Figure out if someone forgot to upmerge some bugfix from 17.04 to master 
>> (happens regularly once or twice each release), for that i use [1] and ignore 
>> the projects that don't do merges from the stable branches to master (you'll 
>> figure out which they are), if they don't want to make my life easy i can't 
>> help them. For that i use [1]
> Ok, that's easy.

Maybe I overdid: I basically up-merged all repositories but one (marble).
Contents should be fine.

>>  * Create the branches, for that i use [2]
> And I will ask for the permissions.

No special permissions required (maybe the script requires a git reset --hard
origin/master before pushing to master, just in case).

>>  * Get the old branches out of CI and the new branches in to CI, for that I've 
>> no idea since the new CI is new and have never done it but hopefully editing 
>> the kde-build-metadata/logical-module-structure should be enough as it was 
>> before.
> You just need to edit logical-module-structure; the jobs are based on the
> definitions there.

Fixed them as well.

>>  * While editing the logical-module-structure take into account that some 
>> repos may have moved from being kdelibs4 based to KF5 based, while you do that 
>> make sure the list at
>> 17.08_Release_Notes is complete
> The list is complete :)

And used as reference.

>>  * Coordinate with Luigi to move the appropiate trunk translations over to 
>> stable
> That's easy too.

Followed the usual steps in the etherpad.

>>  * Edit the topic on #kde-devel
>>  * Email kde-devel mailing list mentioning trunk is open for features and that 
>> people should fix bugs in the new Applications/17.08 branch and merge upwards.
> And probably kde-cvs-announce@

Not kde-cvs-announce but sent email to kde-devel and kde-i18n-doc; Nicolas
changed the topic.

If I screwed up something on i18n or on jenkins we will see it tomorrow.


More information about the release-team mailing list