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

List:       kde-release-team
Subject:    Re: kdepim in KDE Applications 14.12
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-10-30 19:16:23
Message-ID: 2491793.UV9cOxVbur () xps
[Download RAW message or body]

El Dijous, 30 d'octubre de 2014, a les 13:36:28, Kevin Ottens va escriure:
> On Thursday 30 October 2014 08:14:03 laurent Montel wrote:
> > Le Thursday 30 October 2014 01:19:27 Albert Astals Cid a =E9crit :
> > > Hi guys, so Laurent said that for KDE Applications 14.12 we should sh=
ip
> > > 4.x based versions of kdepim*
> > > =

> > > Which brings me to the question, when releasing KDE Applications 14.12
> > > should i branch KDE/4.14 to Applications/14.12 and release that or
> > > should
> > > we keep using the KDE/4.14 branch?
> > =

> > For me it will better to use KDE/4.14 branch.
> > Really I have 4.14 branch + master branch for
> > kdepimlibs/kdepim/kdepim-runtime and I don't want to download a new
> > branch.
> > =

> > It's more easy for me to merge in 4.14 that merge in 4.14 + 14.12 branch
> > and after master
> =

> I guess if you go for 14.12 then the 4.14 branch would get discontinued?

Correct.

> You'd probably still have one branch to deal with, just not the same one
> anymore.

One thing is that by continuing to ship 4.14 branch (instead of a new 14.12=
) =

we'd highlight more than this is pure maintaince instead of "any new featur=
e". =


For example for kdelibs we're just going to ship KDE/4.14.

Now the question, is kdepim* not based in kf5 going to be pure maintiance f=
or =

now?

Cheers,
  Albert

> =

> I understand the concern of "too many branches to deal with", I'm not sure
> it applies here.
> =

> Regards.

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]