[Kde-pim] Re: Opening kdepim master for feature commits, branching kdepim 4.6
Christophe Giboudeaux
cgiboudeaux at gmx.com
Fri Apr 22 11:22:48 BST 2011
On Thursday 21 April 2011 17:32:27 Allen Winter wrote:
>
> What about the following:
> - branch kdepim4/.6 and kdepim-runtime/4.6
> - open kdepim/master and kdepim-runtime/master for new features, strings,
> etc - bug fixes are backported to the 4.6 branches
>
> i.e. the normal situation.
>
> If/when we make a KDEPIM4.6 release, I will use the 4.6 branches. no
> problem at all.
>
> I just need to coordinate with the translators if we want to do this.
>
> Any objections?
>
That sounds a bit late for branching considering that the soft-feature freeze
will happen in 6 days and we still have no idea whether kdepim 4.6 will ever
be released.
Before reopening kdepim, I believe we should answer Kevin's question about the
commit strategy/policy in kdepim: develop in master & cherry-pick in branch
(svn style) or develop new features in staging branches and merge them into
master when new features become mature (kernel style)
Christophe
-------------- 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/20110422/29ff48c9/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/
More information about the kde-pim
mailing list