Re: CI Requirements - Lessons Not Learnt?

2017-01-18 Thread Ben Cooksley
On Thu, Jan 19, 2017 at 6:29 AM, Eike Hein wrote: > > > On 01/17/2017 11:46 PM, Adriaan de Groot wrote: >> But CI has a really important function: it shows us the health of the sources >> for everything; and that's something the release team needs, and the whole >> community can be

Re: CI Requirements - Lessons Not Learnt?

2017-01-18 Thread Albert Astals Cid
El dimecres, 18 de gener de 2017, a les 19:59:46 CET, Friedrich W. H. Kossebau va escriure: > Hi Eike, > > first of all, thanks for turning this into a policy creation process :) > > Am Donnerstag, 19. Januar 2017, 02:29:00 CET schrieb Eike Hein: > > On 01/17/2017 11:46 PM, Adriaan de Groot

Re: CI Requirements - Lessons Not Learnt?

2017-01-18 Thread Alexander Neundorf
On 2017 M01 18, Wed 19:59:46 CET Friedrich W. H. Kossebau wrote: .. > Given this is a policy affecting all of the KDE projects, please first > propose it officially in a separate own thread, with a proper subject. > Perhaps even on kde-community, as kde-core-devel might not be read by many, >

Re: CI Requirements - Lessons Not Learnt?

2017-01-18 Thread Friedrich W. H. Kossebau
Hi Eike, first of all, thanks for turning this into a policy creation process :) Am Donnerstag, 19. Januar 2017, 02:29:00 CET schrieb Eike Hein: > On 01/17/2017 11:46 PM, Adriaan de Groot wrote: > > But CI has a really important function: it shows us the health of the > > sources for everything;

Re: CI Requirements - Lessons Not Learnt?

2017-01-18 Thread Eike Hein
On 01/17/2017 11:46 PM, Adriaan de Groot wrote: > But CI has a really important function: it shows us the health of the sources > for everything; and that's something the release team needs, and the whole > community can be interested in. So "opting out" of CI deprives us of a good > view of