https://bugs.kde.org/show_bug.cgi?id=302923
--- Comment #7 from [email protected] --- The solution is technically well explained. This can work, but changes are very important every where and this need to be introduced and tested while release stage 5.4.0 and 5.5.0 for exemple, if code is ready to review. I propose : 1/ Wait 5.4.0 release before to introduce changes about this topic. 5.4.0 is planed for next week. 2/ Create a git branch to host digiKam core with all you changes. 3/ Post all tests to perform in user space to review the new features with expected results. This must be done here in first stage. 4/ Synchronize step by step your branch with git master. 5/ Depending of feedback, when your code is enough stable and ready for production, merge back your branch to git master. 6/ Post a message in users mailing list to have a final feedback before the release. 7/ Release new digiKam with your changes. What do you think about ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
