[Kde-pim] 4.5 and porting commits / development model

[Thomas McGuire]

Some clarifications since Frank asked on IRC:

> <fosterfeld> quesiton: should i forwardport fixes in 4.5 to trunk myself?

Yes, everyone should do their forwardports themselves if possible. There is no 
magic process that will do that automatically.
When doing the forwardports, please use svnmerge.py, as said in the original 
mail here. svnmerge.py will be set up tomorrow.
If you want to do a forwardport before I set up svnmerge.py, just do it 
manually for now. I'll announce when the setup is done.

Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100707/71416b1c/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/