[Konsole-devel] What is the preferred commit policy for Konsole bugs?
Kurt Hindenburg
kurt.hindenburg at gmail.com
Mon Jan 30 14:13:06 UTC 2012
On Mon, Jan 30, 2012 at 7:21 AM, Jekyll Wu <adaptee at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Method A: fix bug first in master branch, then backport(git
> cherry-pick) it into KDE/4.x branch
> Method B: fix bug first in KDE/4.x branch, then merge KDE/4.x into master
>
> Hi,
I use method A.
1. If something breaks, I'd rather it be in master
2. It is bad if a regression or other bad issues go out to public in a .x.y
release.
3. I think more people run the master branch and are more likely to catch
issues
4. master doesn't have a timetable, while the 4.x branch does.
Regards,
Kurt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/konsole-devel/attachments/20120130/70d90643/attachment.html>
More information about the konsole-devel
mailing list