Re: kactivities master becomes Qt5/KF5-based
On Wed, January 29, 2014 00:02:09 Ivan Čukić wrote: Ping, 4.13 is looming over. If you want to make it so there's no new releases of 4.12.x anymore and master is KF5 based, please discuss now. Personally I'd suggest against it since seems that even if we dicussed for that happening to kde-workspace people did not get the memo and got angry, so unless you have a huge itch to make it happen i'd just do with kactivities the same we do with kdelibs. I've been procrastinating. We can't do the same thing as with kdelibs. Simply because those were split into separate repositories where masters are qt5/kf5-based. KActivities is already in a separate repository. I think Albert would be referring to when kdelibs was tracking both KDE 4 and KF5 Frameworks development (before the KF5 repo splits occurred). If we decide to wait after 4.13, the next release of Plasma will have to use a non-master-based kactivities which I'm not sure is a good idea. Naturally, I am open to suggestions. We already track branch groups for the build.kde.org CI infrastructure and for kdesrc-build users, which simply maps which 'role' is being build for to the needed repo branch to use. It's visible in the kde-build-metadata repo, and should make it easy enough to manage (this is used in the same kf5-qt5-build-include that dfaure and others are maintaining for the kdesrc-build KF5 config). Regards, - Michael Pyne signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
El Dilluns, 21 d'octubre de 2013, a les 19:14:23, Ivan Čukić va escriure: Well, to be honest, if you don't want a 4.13 release i'd prefer you actually use master for KF5. Otherwise people might random-commit fixes to master and then wonder why they never got into a release, so the two situations i think make sense are: People don't really contribute to kactivities, but I agree. A) wait until we branch KDE/4.12 and then use master for KF5, not release kactivities 4.13 and maybe release more 4.12.x of kactivities than the rest of the SC if there are fixes for it This is what I was thinking of - until we branch, the branch is called frameworks, and after that it will be moved to master. Am I making any sense? Perfect sense, as usual mate :) Ping, 4.13 is looming over. If you want to make it so there's no new releases of 4.12.x anymore and master is KF5 based, please discuss now. Personally I'd suggest against it since seems that even if we dicussed for that happening to kde-workspace people did not get the memo and got angry, so unless you have a huge itch to make it happen i'd just do with kactivities the same we do with kdelibs. Cheers, Albert Cheers, Ivan ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
Ping, 4.13 is looming over. If you want to make it so there's no new releases of 4.12.x anymore and master is KF5 based, please discuss now. Personally I'd suggest against it since seems that even if we dicussed for that happening to kde-workspace people did not get the memo and got angry, so unless you have a huge itch to make it happen i'd just do with kactivities the same we do with kdelibs. I've been procrastinating. We can't do the same thing as with kdelibs. Simply because those were split into separate repositories where masters are qt5/kf5-based. KActivities is already in a separate repository. If we decide to wait after 4.13, the next release of Plasma will have to use a non-master-based kactivities which I'm not sure is a good idea. Naturally, I am open to suggestions. Cheers, Ivan -- The problem with object-oriented languages is they’ve got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana. -- Joe Armstrong ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
kactivities master becomes Qt5/KF5-based
Hi all, Following kde-workspace (and stealing a few sentences from that announcement), we're planning to merge the frameworks-scratch branch of kactivities into master later today. That means if you're building 4.x branch of Plasma yourself from Git, you should switch to the KDE/4.11 branch. The build will fail otherwise, so you will notice. This was a public service announcement. (And you can ask questions here.) If somebody can help with the metadata and kdesrc-build, it would be appreciated - I don't want to screw up something. For the KF5 kdesrc-build, I'm confident I can manage, but for the 4.x branch not so much. Cheers, Ivan -- There are no such things as applied sciences, only applications of science. -- Louis Pasteur ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
Please no. We have a 4.12 release to make in 2 weeks and back when we did the 4.12 planning the only agreed repo to be freezed for 4.11 was kde-workspace. What about doing an early KDE/4.12 branch from master so that the release can continue as planned, while not slowing us down for further development? Cheers, Ivan -- Those people who think they know everything are a great annoyance to those of us who do. -- Isaac Asimov ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
Hi all, Following kde-workspace (and stealing a few sentences from that announcement), we're planning to merge the frameworks-scratch branch of kactivities into master later today. That means if you're building 4.x branch of Plasma yourself from Git, you should switch to the KDE/4.11 branch. The build will fail otherwise, so you will notice. This was a public service announcement. (And you can ask questions here.) Please no. We have a 4.12 release to make in 2 weeks and back when we did the 4.12 planning the only agreed repo to be freezed for 4.11 was kde-workspace. Cheers, Albert If somebody can help with the metadata and kdesrc-build, it would be appreciated - I don't want to screw up something. For the KF5 kdesrc-build, I'm confident I can manage, but for the 4.x branch not so much. Cheers, Ivan -- There are no such things as applied sciences, only applications of science. -- Louis Pasteur ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
El Dilluns, 21 d'octubre de 2013, a les 14:02:42, Ivan Čukić va escriure: Please no. We have a 4.12 release to make in 2 weeks and back when we did the 4.12 planning the only agreed repo to be freezed for 4.11 was kde-workspace. What about doing an early KDE/4.12 branch from master so that the release can continue as planned, while not slowing us down for further development? I was planning to branch master into KDE/4.12 after October 30 and before November 6. Would that work for you? Also it means that you don't want a 4.13.x for kactivities, right? Cheers, Albert Cheers, Ivan ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
I was planning to branch master into KDE/4.12 after October 30 and before November 6. Forget about it. Decided not to create problems - I'll use the same name for the branch as kdelibs do for the time being - frameworks :) Also it means that you don't want a 4.13.x for kactivities, right? Yes. The development of 4.x branch is frozen for some time now. -- Cheerio, Ivan -- While you were hanging yourself on someone else's words Dying to believe in what you heard I was staring straight into the shining sun ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
El Dilluns, 21 d'octubre de 2013, a les 18:43:20, Ivan Čukić va escriure: I was planning to branch master into KDE/4.12 after October 30 and before November 6. Forget about it. Decided not to create problems - I'll use the same name for the branch as kdelibs do for the time being - frameworks :) Also it means that you don't want a 4.13.x for kactivities, right? Yes. The development of 4.x branch is frozen for some time now. Well, to be honest, if you don't want a 4.13 release i'd prefer you actually use master for KF5. Otherwise people might random-commit fixes to master and then wonder why they never got into a release, so the two situations i think make sense are: A) wait until we branch KDE/4.12 and then use master for KF5, not release kactivities 4.13 and maybe release more 4.12.x of kactivities than the rest of the SC if there are fixes for it or B) use frameworks for KF5, keep master open for 4.13 and just release it like the rest of the SC for 4.13 even if there were no changes. I do think A) makes sense if you don't have a focus on 4.x anymore. Am I making any sense? Cheers, Albert ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: kactivities master becomes Qt5/KF5-based
Well, to be honest, if you don't want a 4.13 release i'd prefer you actually use master for KF5. Otherwise people might random-commit fixes to master and then wonder why they never got into a release, so the two situations i think make sense are: People don't really contribute to kactivities, but I agree. A) wait until we branch KDE/4.12 and then use master for KF5, not release kactivities 4.13 and maybe release more 4.12.x of kactivities than the rest of the SC if there are fixes for it This is what I was thinking of - until we branch, the branch is called frameworks, and after that it will be moved to master. Am I making any sense? Perfect sense, as usual mate :) Cheers, Ivan -- So much complexity in software comes from trying to make one thing do two things. -- Ryan Singer ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
