[Kde-pim] kdepim in KDE Applications 14.12

[Christian Mollekopf]

On Friday 31 October 2014 13.40:24 laurent Montel wrote:
> Le Friday 31 October 2014 11:47:57 David Jarvie a écrit :
> > On Thu, October 30, 2014 8:24 pm, Albert Astals Cid wrote:
> > > El Dijous, 30 d'octubre de 2014, a les 20:41:43, laurent Montel va
> > > 
> > > escriure:
> > >> Le Thursday 30 October 2014 20:16:23 Albert Astals Cid a écrit :
> > >> > 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 écrit :
> > >> > > > > Hi guys, so Laurent said that for KDE Applications 14.12 we
> > >> 
> > >> should
> > >> 
> > >> > > > > ship
> > >> > > > > 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 feature".
> > >> > 
> > >> > 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
> > >> 
> > >> > for now?
> > >> 
> > >> No dev until now just maintiance.
> > > 
> > > If it's going to be just maintaince i think i actually prefer not having
> > > a14.12 branch and just using a longer lived KDE/4.14
> > > 
> > > Is that fine for you guys?
> > 
> > Until all the kdepim applications are released for kf5, I don't think that
> > the KDE 4 branch should be restricted to maintenance only.
> 
> I am against that there is new feature in kde4 kdepim.
> Otherwise I will need to port all to kf5.
> So no, kde4 branch is closed for new features.
> 
> Otherwise nobody will work on kf5 and for the moment there is just me which
> works on kf5 kdepim.
> 
> For new string changes you can ask to kde-doc to allow a new string.
> 

IMO it wouldn't be a problem to allow new features in 4.14, but of course it's 
the responsibility of the person that adds the feature to ensure it makes it 
into master. It clearly shouldn't be your responsibility (or any single 
person's for that matter), to port other peoples features.

I'd rather allow some new features in 4.14 to keep people happy, than rush a 
release of a KF5 based solution. Even though you're currently paving the way 
mostly alone for the rest of us (thanks!), we'll definitely move to the next 
version when we get to it =)

Cheers,
Christian

_______________________________________________
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/