New framework: KXmlRpcClient

[Albert Astals Cid]

El Dimecres, 25 de febrer de 2015, a les 13:23:42, David Faure va escriure:
> On Wednesday 28 January 2015 20:01:45 Albert Astals Cid wrote:
> > El Dimecres, 28 de gener de 2015, a les 16:17:53, David Faure va escriure:
> > > On Monday 26 January 2015 15:25:34 Daniel Vrátil wrote:
> > > > Bump.
> > > > 
> > > > We would really love to get this to 5.7, so unless anyone objects,
> > > > I'll
> > > > wait  couple days, then file a sysadmin request and flip the 'Release'
> > > > flag
> > > > in the YAML file to true.
> > > 
> > > Did  you check the frameworks checklist?
> > > 
> > > https://community.kde.org/Frameworks/CreationGuidelines
> > > 
> > > One of the items is "green in CI", which it's not.
> > > http://build.kde.org/view/Frameworks/job/kxmlrpcclient_master_qt5/
> > > 
> > > 
> > > I took care of adding this job to view/Frameworks, but it seems a
> > > kxmlrpcclient_stable_qt5 is missing, compared to the other frameworks?
> > 
> > Well it hasn't had a stable release yet, so why there should be a _stable
> > job?
> 
> I thought _stable was about the underlying Qt 5 version.

_stable jobs exist because on how our jenkins architecture work, you can't 
have plasma_desktop_stable job building against kcoreaddons_master, you need 
it to be kcoreaddons_stable

Now, you're right that they also build against an older Qt5, and that's good, 
but it's not the main reason the _stable jobs are.

I'd prefer to make sure we don't have a kxmlrpcclient_stable job until it's 
released, that way if by mistake other _stable jobs try to use it, they will 
fail, signaling they are trying to build against an unreleased lib.

What do you think?

Cheers,
  Albert