KDE Gear 21.12 release branches created
Please make sure you commit anything you want to end up in the 21.12 releases to them. We're already past the dependency freeze, so no new dependencies or increasing of dependency versions in the stable branches. The feature freeze, tagging and release of the beta (21.11.80) is in four days,11 November. Next interesting dates: November 25: 21.12 RC (21.11.90) Tagging and Release December 2: 21.12 Tagging December 9: 21.12 Release Complete Schedule: https://community.kde.org/Schedules/KDE_Gear_21.12_Schedule Regards, Heiko
Re: Sub: getting started with KDE community
Dear Sy Sagar, Here you can find some information on different things you could look into. https://community.kde.org/Get_Involved I'd recommend you look into our products and see something you'd like to work on improving. It will help you find the answers you are looking for. Good luck! Aleix On Sun, Nov 7, 2021 at 6:48 AM Sy Sagar wrote: > > Hi, I am a first year college student and new to the open source community ; > I am interested in the KDE community projects and want to genuinely > contribute to it. I have an intermediate knowledge of C++ and have recently > been into DSA ( link list , stacks, queues, arrays, trees , some parts of > graph). Please guide me to the right path as per my skills so that I can > begin working efficiently in any project development and learn more in my > journey of contribution in the open source community. Thank you! >
How do you label code to be deleted in KF6?
I would like to have some members of KCalendarCore's incidence classes removed during the transition from KF5 to KF6, and I'd like to be sure that the changes won't be missed in the excitement. Do you have some preferred way to label such changes? For example, is there some `#if` statement that can be wrapped around the code, such that it will be compiled into KF5 but compiled out of KF6?
