Fwd: Forward porting policy

[David Faure]

On Thursday 26 January 2012 16:12:22 Dario Freddi wrote:
> Forwarding to framework, hoping somebody here cares...

I don't see the relation. I could answer all these questions for kdelibs, but 
your question is about kde-workspace, which isn't part of the frameworks effort 
at all, at the moment.

> ---------- Forwarded message ----------
> From: Dario Freddi <drf54321 at gmail.com>
> Date: 2012/1/20
> Subject: Forward porting policy
> To: kde-core-devel at kde.org
> 
> 
> Howdy,
> 
> 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)?
> 
> Thanks
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5