A new request with request id 15001 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :

Title : Koha-devel Digest, Vol 191, Issue 13
Category :
Description :
Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Re: Workflow improvement suggestions for security releases
(Kyle Hall)
2. Re: Built-in offline circulation interface (Kyle Hall)
3. Re: Built-in offline circulation interface (BFL Catalog)


----------------------------------------------------------------------

Message: 1
Date: Tue, 19 Oct 2021 14:13:39 -0400
From: Kyle Hall <kyle.m.hall@gmail.com>
To: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Cc: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Workflow improvement suggestions for
    security releases
Message-ID:
    <CACpVHfz0Za1JsQpfkVRUxsi0DQMokb8dvpiMBcZqyH1gb2RPmQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

> For 22.05, Calalyst and Wainui are offering to maintain 19.11, and
> there is a gap as there is no candidate for 20.05.
> So it's kind of our first LTS :)
>

I suppose we need to understand Catalyst's upgrade strategy a bit more. It
we as a community are going to do LTS, we need to really commit to it.
19.11 will be two years out as of the 21.11 release.
Ubuntu LTS releases are every two years. If my math is correct, that would
mean that 21.11 would be the next LTS release. Does Catalyst plan on
upgrading from 19.11 to 21.11?
I'm curious how many libraries would utilize an LTS release and upgrade
bi-annually.
Do we have any metrics on what is being pulled from the community apt
server? If not, is it possible to add tracking?

In the first step I was suggesting a script in the release-tools repo
> to auto-apply a patch set on the different stable branches.
> But then, our imagination is the limit :)
>

That sounds good to me! I can imagine a new bugzilla field for "Fails to
apply to" that would be a list of release branches ( 21.05.x, 20.11.x, etc
) so we would be aware.

Kyle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/82d20196/attachment-0001.htm>

------------------------------

Message: 2
Date: Tue, 19 Oct 2021 14:14:53 -0400
From: Kyle Hall <kyle.m.hall@gmail.com>
To: David Cook <dcook@prosentient.com.au>
Cc: Cab Vinton <bibliwho@gmail.com>, Koha Devel
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Built-in offline circulation interface
Message-ID:
    <CACpVHfz64Ep+oxrKiaKpsjmCt_0ktv2q=yhkU67RWygW7OBcnQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Indeed! I know many ByWater partners use the desktop application.
I'd go so far to say I'm not aware of any ByWater partners using the FF
plugin or the HTML5 version at this time.

Kyle

---
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )


On Sun, Oct 17, 2021 at 8:21 PM <dcook@prosentient.com.au> wrote:

> Does that mean that you actually have a lot of people using the desktop
> application? Interesting!
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Koha-devel <koha-devel-bounces@lists.koha-community.org> *On
> Behalf Of *Kyle Hall
> *Sent:* Monday, 18 October 2021 9:49 AM
> *To:* Cab Vinton <bibliwho@gmail.com>
> *Cc:* Koha Devel <koha-devel@lists.koha-community.org>
> *Subject:* Re: [Koha-devel] Built-in offline circulation interface
>
>
>
> The desktop application has been rocksolid for many years now! I’ve always
> shied away from the browser based I’ll find circulations simply because if
> something goes wrong, like the browser crashing and losing data or
> something, there’s no way to get that data back. The offline circulation
> desktop application writes everything to file as you perform actions so the
> data doesn’t get lost in the event of a crash.
>
>
>
> Kyle
>
>
>
> On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho@gmail.com> wrote:
>
> Fwiw, we'd somehow missed that there was a built-in capability/ system
> preference. Always assumed the utility was our only option.
>
> This functionality is an important part of Koha's feature set, so +1
> to always having at least one up-to-date option available.
>
> Cheers,
>
> Cab Vinton, Director
> Plaistow Public Library
> Plaistow, NH
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
> --
>
> ---
>
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/e0d538ac/attachment-0001.htm>

------------------------------

Message: 3
Date: Tue, 19 Oct 2021 14:19:32 -0400
From: BFL Catalog <catalog@bfli.org>
To: Kyle Hall <kyle.m.hall@gmail.com>
Cc: David Cook <dcook@prosentient.com.au>, Koha Devel
    <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Built-in offline circulation interface
Message-ID:
    <CAMigdodemb7KNiCuVcfo4S6VnA6n4Gz4E1eZso-3geh444t08Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Desktop application has gotten us out of a couple of tight spots so we
could still operate as a lending library while we had a complete loss of
all things internet.

Wendy Sharkey
Head of Circulation/ Cataloging and IT
Bennington Free Library
101 Silver Street
Bennington, VT 05201
(802) 442-9051


On Tue, Oct 19, 2021 at 2:15 PM Kyle Hall <kyle.m.hall@gmail.com> wrote:

> Indeed! I know many ByWater partners use the desktop application.
> I'd go so far to say I'm not aware of any ByWater partners using the FF
> plugin or the HTML5 version at this time.
>
> Kyle
>
> ---
> http://www.kylehall.info
> ByWater Solutions ( http://bywatersolutions.com )
> Meadville Public Library ( http://www.meadvillelibrary.org )
> Crawford County Federated Library System ( http://www.ccfls.org )
>
>
> On Sun, Oct 17, 2021 at 8:21 PM <dcook@prosentient.com.au> wrote:
>
>> Does that mean that you actually have a lot of people using the desktop
>> application? Interesting!
>>
>>
>>
>> David Cook
>>
>> Senior Software Engineer
>>
>> Prosentient Systems
>>
>> Suite 7.03
>>
>> 6a Glen St
>>
>> Milsons Point NSW 2061
>>
>> Australia
>>
>>
>>
>> Office: 02 9212 0899
>>
>> Online: 02 8005 0595
>>
>>
>>
>> *From:* Koha-devel <koha-devel-bounces@lists.koha-community.org> *On
>> Behalf Of *Kyle Hall
>> *Sent:* Monday, 18 October 2021 9:49 AM
>> *To:* Cab Vinton <bibliwho@gmail.com>
>> *Cc:* Koha Devel <koha-devel@lists.koha-community.org>
>> *Subject:* Re: [Koha-devel] Built-in offline circulation interface
>>
>>
>>
>> The desktop application has been rocksolid for many years now! I’ve
>> always shied away from the browser based I’ll find circulations simply
>> because if something goes wrong, like the browser crashing and losing data
>> or something, there’s no way to get that data back. The offline circulation
>> desktop application writes everything to file as you perform actions so the
>> data doesn’t get lost in the event of a crash.
>>
>>
>>
>> Kyle
>>
>>
>>
>> On Sat, Oct 16, 2021 at 8:12 AM Cab Vinton <bibliwho@gmail.com> wrote:
>>
>> Fwiw, we'd somehow missed that there was a built-in capability/ system
>> preference. Always assumed the utility was our only option.
>>
>> This functionality is an important part of Koha's feature set, so +1
>> to always having at least one up-to-date option available.
>>
>> Cheers,
>>
>> Cab Vinton, Director
>> Plaistow Public Library
>> Plaistow, NH
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.org
>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : https://www.koha-community.org/
>> git : https://git.koha-community.org/
>> bugs : https://bugs.koha-community.org/
>>
>> --
>>
>> ---
>>
>> http://www.kylehall.info
>> ByWater Solutions ( http://bywatersolutions.com )
>> Meadville Public Library ( http://www.meadvillelibrary.org )
>> Crawford County Federated Library System ( http://www.ccfls.org )
>>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211019/ab6ed35a/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


------------------------------

End of Koha-devel Digest, Vol 191, Issue 13
*******************************************


NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.