Hello,
On Thursday 22 May 2014 21:08:05 Alex Merry wrote:
There are currently four frameworks that are yellow (for between 6 hours and
8 days). kdelibs4support has had 3 commits (not counting those by scripty)
since it broke that have done nothing to fix the issue.
If we claim that our
On 03/06/14 17:24, Kevin Ottens wrote:
I see room for improvement in what gets evaluated when (like ability to run a
patch in jenkins as part of the review process), I'm just stuck on the term
enforcing there, not sure what you have in mind.
Neither am I, to be honest. It just feels like
El Divendres, 23 de maig de 2014, a les 07:19:59, Martin Gräßlin va escriure:
On Thursday 22 May 2014 21:08:05 Alex Merry wrote:
There are currently four frameworks that are yellow (for between 6 hours
and 8 days). kdelibs4support has had 3 commits (not counting those by
scripty) since it
On Friday 23 May 2014 19:53:38 Albert Astals Cid wrote:
El Divendres, 23 de maig de 2014, a les 07:19:59, Martin Gräßlin va
escriure:
On Thursday 22 May 2014 21:08:05 Alex Merry wrote:
There are currently four frameworks that are yellow (for between 6 hours
and 8 days). kdelibs4support
There are currently four frameworks that are yellow (for between 6 hours and 8
days). kdelibs4support has had 3 commits (not counting those by scripty) since
it broke that have done nothing to fix the issue.
If we claim that our release schedule means more stability because of our
review
On Fri, May 23, 2014 at 8:08 AM, Alex Merry alex.me...@kde.org wrote:
There are currently four frameworks that are yellow (for between 6 hours and 8
days). kdelibs4support has had 3 commits (not counting those by scripty) since
it broke that have done nothing to fix the issue.
If we claim
