At 09:59 AM 12/11/2013 +1300, Liz Rea wrote:
On 11/12/13 05:40, Owen Leonard wrote:
>> [4] Upgrade the version of Bootstrap we use to 3.x.
> As I mentioned in IRC today the primary caveat for this goal is that
> Bootstrap 3 says it "drops support for Internet Explorer 7 and Firefox
> 3.6." Howev
Some plans that ByWater (Kyle, Jesse, etc.) has for 3.16 (or at least make
sure our patches are out there).
Elastic Search - which Chris talked about.
New catalogers interface - which Jesse Weaver has been working on and we're
getting closer and closer to having that ready to submit. (Jesse did
Greetings,
If it means broken functionality, that is a problem for us.
If it means graceful degradation, that's more acceptable.
Yes and yes.
I'll be doing some investigation, but I think we need some opinions
from others about what level of support we need to offer for IE7
and FF 3.6.
IE
Hi All
In addition to the goals Galen has mentioned.
Catalyst and Bywater are working on adding ElasticSearch as an option
for searching in Koha.
It will of course not remove Zebra, but will provide the option of
using it as a search tool instead.
The brief plan is
Write code, so that if Elasti
On 11/12/13 05:40, Owen Leonard wrote:
>> [4] Upgrade the version of Bootstrap we use to 3.x.
> As I mentioned in IRC today the primary caveat for this goal is that
> Bootstrap 3 says it "drops support for Internet Explorer 7 and Firefox
> 3.6." However, it doesn't explicitly say what "dropping su
On 11 December 2013 08:46, Kyle Hall wrote:
>> Developers will (and should) have to do most of the sign offs, what we
>> might need is a better way to 'swap' patches. I sign off yours, you
>> sign off mine for example.
>
>
> I completely agree. I recall you were working on some sort of Karma syste
>
> I can understand that Galen does not always have the time to examine each
> patch when it enters PQA. But I would really like to see here more-or-less
> FIFO (first in, first out). First out could of course mean Failed QA or
> Discussion, but at least a change of state with some comments. The c
>
> Developers will (and should) have to do most of the sign offs, what we
> might need is a better way to 'swap' patches. I sign off yours, you
> sign off mine for example.
>
I completely agree. I recall you were working on some sort of Karma system
to track sign-offs and QA? Has then gotten off
On 11/12/2013 3:08 am, "Marcel de Rooy" wrote:
>
> Hi Jonathan
>
>
>
> > The number of patches waiting for QA has decreased. This could be
explained by the efforts of the QA team, but
>
> > also by the decrease of SO patches - and thus by the decrease of
patches going into the QA queue. The stack
> [4] Upgrade the version of Bootstrap we use to 3.x.
As I mentioned in IRC today the primary caveat for this goal is that
Bootstrap 3 says it "drops support for Internet Explorer 7 and Firefox
3.6." However, it doesn't explicitly say what "dropping support"
means. If it means broken functionality
At 10:53 AM 12/10/2013 +, MJ Ray wrote:
[snip]
I would prefer Koha to have something like About: Check for Updates,
rather than any set-by-default feature.
+1
Thanks - Paul
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http:/
Hi Jonathan
> The number of patches waiting for QA has decreased. This could be explained
> by the efforts of the QA team, but
> also by the decrease of SO patches - and thus by the decrease of patches
> going into the QA queue. The stack of
> patches waiting for SO is closed to 200, and my
Christopher Nighswonger wrote:
> The last time I did a fresh Ubuntu install, (a few weeks ago) I was offered
> the option of automagic updates (either full or just security). I'd bet
> Debian has this option too (probably other distros as well).
And I bet debian has it switched off by default - I
13 matches
Mail list logo
