Forward porting policy

Dario Freddi drf54321 at
Fri Jan 20 14:21:54 GMT 2012


I just pushed a fix to KDE/4.8 in workspace. Now, when trying to
forward-port as usual, a variety of commits by scripty, and a commit
from a fellow developer, were merged as well. Which raises two
questions that boggle me since a while:

1. Should 4.x always be fully merged into master? Just to avoid
merging to master other commits from other developers which weren't
meant to be there
2. Are commits from scripty ok to be merged?
3. Should I just commit to 4.8 or wait for somebody else to do the
merge periodically (optimal solution IMHO)?


More information about the kde-core-devel mailing list