[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Fwd: Forward porting policy
From:       Dario Freddi <drf54321 () gmail ! com>
Date:       2012-01-26 15:12:22
Message-ID: CAFFVnfPjth99KUWZQSWq_UP=_OeJ6HikFNbjxVCCZqRQPX=M=w () mail ! gmail ! com
[Download RAW message or body]

Forwarding to framework, hoping somebody here cares...


---------- Forwarded message ----------
From: Dario Freddi <drf54321@gmail.com>
Date: 2012/1/20
Subject: Forward porting policy
To: kde-core-devel@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@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
[prev in list] [next in list] [prev in thread] [next in thread]