Hi Cristian, just out of sheer curiosity: Once someone decides to release 4.7.0 one would have to start picking features from branch master and make them build nicely in a new 4.7 branch right? So, I am just wondering how to make sure that you don't forget anything, because you have separate branches for the 4.6 series with all 4.6.n in there, but master is full of various commits. How do you determine which changesets have actually already landed in the new 4.7 branch?
Greets, Marko _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
