Re: Review Request 129806: Update the list of KCModules

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129806/ --- (Updated Jan. 12, 2017, 7:51 a.m.) Status -- This change has been

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 12, 2017 at 4:54 AM, Martin Gräßlin wrote: > Am 2017-01-11 10:46, schrieb Ben Cooksley: >> >> On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin >> wrote: >>> >>> >>> >>> Am 10. Januar 2017 22:42:35 MEZ schrieb Ben Cooksley :

Re: CI Requirements - Lessons Not Learnt?

On Thu, Jan 12, 2017 at 3:23 AM, Scarlett Clark wrote: > > > On Wed, Jan 11, 2017 at 4:40 AM, Jan Kundrát wrote: >> >> On středa 11. ledna 2017 6:57:50 CET, Martin Gräßlin wrote: >>> >>> That doesn't work. Such inflexibility take away the advantage

Re: CI Requirements - Lessons Not Learnt?

Am 2017-01-12 04:00, schrieb Kevin Kofler: Martin Gräßlin wrote: Email threads don't work to codify such requirements. What we need is something like an "announce new dependency to sysadmin freeze" prior to the dependency freeze in the release schedule. That's what I mean with codifying it.

Re: CI Requirements - Lessons Not Learnt?

Am 2017-01-12 04:10, schrieb Kevin Kofler: Martin Gräßlin wrote: #if 0 // code already written, but not enabled as CI doesn't have it #endif If you already have this, then why don't you just write: #ifdef HAVE_FOO_1_23 or #if HAVE_FOO_1_23 with an appropriate #cmakedefine instead of #if 0?

Re: CI Requirements - Lessons Not Learnt?

Martin Gräßlin wrote: > #if 0 > // code already written, but not enabled as CI doesn't have it > #endif If you already have this, then why don't you just write: #ifdef HAVE_FOO_1_23 or #if HAVE_FOO_1_23 with an appropriate #cmakedefine instead of #if 0? Then things will just work and everybody

Re: CI Requirements - Lessons Not Learnt?

Martin Gräßlin wrote: > Email threads don't work to codify such requirements. What we need is > something like an "announce new dependency to sysadmin freeze" prior to > the dependency freeze in the release schedule. That's what I mean with > codifying it. We need to have it in a way where devs

Re: CI Requirements - Lessons Not Learnt?

Alexander Neundorf wrote: > there would be the pragmatic solution to (I know distros don't like that > etc. etc.) to include a copy of the required xkbcommon library and link it > statically if no matching version is found on the system. There could be > an extra cmake switch to enable it... For

Re: Review Request 129806: Update the list of KCModules

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129806/#review101960 --- Ship it! Ship It! - Michael Pyne On Jan. 11, 2017,

Re: CI Requirements - Lessons Not Learnt?

About distributions that want to backport Plasma master instead of sticking to Plasma LTS: It's their problem and I wouldn't care if they complain about dependencies now that we have a solution for them (Plasma LTS). If we still need to worry about not bumping dependencies in Plasma master, then

Re: CI Requirements - Lessons Not Learnt?

Hey, > how about some simple rule like "new dependencies every first of the month", > and 1 week notice. For the developer this would mean in the worst case 5 > weeks waiting, which is probably quite a lot. I think this is not necessary. Because sysadmins can comment the dependency bump. I

Review Request 129806: Update the list of KCModules

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/129806/ --- Review request for KDE Base Apps and David Faure. Repository: konqueror

Re: CI Requirements - Lessons Not Learnt?

I have no problem adding a rolling release image to the stack like arch. Perhaps have this build master and stable - > lts image ? Scarlett On Wed, Jan 11, 2017 at 8:11 AM, Martin Gräßlin wrote: > Am 2017-01-11 13:40, schrieb Jan Kundrát: > >> On středa 11. ledna 2017

Re: CI Requirements - Lessons Not Learnt?

Am 2017-01-11 13:40, schrieb Jan Kundrát: On středa 11. ledna 2017 6:57:50 CET, Martin Gräßlin wrote: That doesn't work. Such inflexibility take away the advantage of having a CI. What base system(s) do you prefer to target as a developer, Martin? We release software which will be combined

Re: CI Requirements - Lessons Not Learnt?

Am 2017-01-11 11:10, schrieb Eike Hein: So my view of the situation is that we have a bunch of desires and needs, and we need to sort them. Here's a couple I can reasily identify: * We want to have a working CI that gives us useful results * We want to have developer flexibility in terms of

Re: CI Requirements - Lessons Not Learnt?

Am 2017-01-11 10:46, schrieb Ben Cooksley: On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin wrote: Am 10. Januar 2017 22:42:35 MEZ schrieb Ben Cooksley : On Mon, Jan 9, 2017 at 8:22 AM, Martin Gräßlin wrote: Am 6. Januar 2017

Re: CI Requirements - Lessons Not Learnt?

On Wed, Jan 11, 2017 at 4:40 AM, Jan Kundrát wrote: > On středa 11. ledna 2017 6:57:50 CET, Martin Gräßlin wrote: > >> That doesn't work. Such inflexibility take away the advantage of having a >> CI. >> > > What base system(s) do you prefer to target as a developer, Martin? > > A

Re: CI Requirements - Lessons Not Learnt?

On středa 11. ledna 2017 6:57:50 CET, Martin Gräßlin wrote: That doesn't work. Such inflexibility take away the advantage of having a CI. What base system(s) do you prefer to target as a developer, Martin? A CI system can have different sets of base images for different projects (and

Re: CI Requirements - Lessons Not Learnt?

So my view of the situation is that we have a bunch of desires and needs, and we need to sort them. Here's a couple I can reasily identify: * We want to have a working CI that gives us useful results * We want to have developer flexibility in terms of using and catering latest dependencies *

Re: CI Requirements - Lessons Not Learnt?

On Wed, Jan 11, 2017 at 6:57 PM, Martin Gräßlin wrote: > > > Am 10. Januar 2017 22:42:35 MEZ schrieb Ben Cooksley : >>On Mon, Jan 9, 2017 at 8:22 AM, Martin Gräßlin >>wrote: >>> >>> >>> Am 6. Januar 2017 17:46:30 MEZ schrieb Alexander