[Koha-devel] Configuration inheritance/override

[David Cook]

Hi all,

 

I think that we've all noticed that it's easy to add a new configuration
item to koha-conf.xml for new instances, but that it's much harder to update
koha-conf.xml when upgrading existing instances.

 

A strategy that I (and others) have used on other projects is to have a
core/base configuration file with defaults, and then the local config file
is used to override those defaults on a per-instance basis. 

 

The core/base config file can be replaced as part of a Debian package
upgrade, and it can be used to push out updated configuration to all
instances with 1 click.

 

This methodology also means that the local config file can often be fairly
small too as it's only overriding specific configuration items. 

 

Anyway, it's easier said than done for Koha, but it's a thought, especially
as we move forward. I know this is a problem that we bump into often in Koha
and it would help to solve it.

 

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

 

___
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/

Re: [Koha-devel] A case against our release dates

[David Cook]

I think that it never hurts to review an established tradition!

 

In the southern hemisphere, I often catch up on a lot of work in December as 
many clients go on holiday early, and then I have my summer holidays in 
January. In April, I’ll take the latest point release of the November version 
(e.g. XX.11.03), and base local work off that, since it’s new but not *too new* 
(ie buggy). 

 

If the community did releases in February/March and August/September… I’d 
probably use the August/September release as my local code base for 
February-April since February/March would be “too new”/bleeding edge for me. 

 

Of course, August/September is right after northern hemisphere summer holidays… 
which might mean it’s a smaller release or it’s less stable as it has fewer 
eyes on it… 

 

And if the release was in February/March, would Hackfest be about setting the 
path for the next cycle, or would it be fixing all the bugs in the release that 
just came out a few weeks earlier?

 

Would December Christmas holidays negatively impact a February/March release?

 

Maybe it’s just human nature to leave big changes too close to the release 
date? We always think there will be lots of time, and then we rush to do things 
at the last minute? 

 

In any case, I think it’s worthwhile reviewing what we’re doing.

 

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  On Behalf Of 
Tomas Cohen Arazi
Sent: Friday, 2 June 2023 1:52 AM
To: Philippe Blouin 
Cc: koha-devel 
Subject: Re: [Koha-devel] A case against our release dates

 

My personal feeling is we should have a release right before the hackfest. So 
the hackfest sets the path for the next cycle. That could mean moving the 
hackfest a couple a bit later too

 

Add for the second part of the year, I'm not sure yet. I just have the 
perception everyone is out in the months we are expected to do the bigger 
changes, and we end up doing them close to the release date.

 

El jue, 1 jun 2023 12:46, Philippe Blouin mailto:philippe.blo...@inlibro.com> > escribió:

Of course I'm coming with my northern hemisphere perspective, and have no horse 
in the race really as being far from RM, but I always thought those dates were 
the best available.

Seems earlier (04, april) makes it closer to the hackfest you referred.  Later 
makes it closer to summer holidays.

Were you considering breaking the equal split in time, having a small and a big 
release each year?  November for the big, and march for the small, the hackfest 
starting the next cycle ?  Thinking outside the box...

 

Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blo...@inlibro.com   

inLibro | pour esprit libre | www.inLibro.com   

On 2023-06-01 07:35, Tomas Cohen Arazi wrote:

Hi all. Having served as Release Manager for the project a couple times, I'd 
like to ask y'all to think about the dates we've chosen and have stuck to the 
last few years for our releases. 

 

I know they are somehow aligned with our regular yearly meetings, and one each 
semester. But my experience says:

 

- We all want to implement things we discuss in the Hackfest, but the release 
is too close. So we either push too late in the cycle, or need to cool down our 
brains/ideas for 'after the release in two months'.

- The other scenario, which I suffered a lot recently (and will soon) is summer 
holidays in the northern hemisphere: you're all out when we should be pushing 
the riskier things to have enough time to fix things, and we end up rushing 
things... on the last third of the cycle.


 

I don't have a proposal right now, but wanted to say my perception is the dates 
are not ideal as-is. And hear back from you all.

 

Cheers!

 

-- 

Tomás Cohen Arazi

Theke Solutions (http://theke.io  )
✆ +54 9351 3513384
GPG: B2F3C15F

 

___
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/

___
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/

Re: [Koha-devel] A case against our release dates

[Tomas Cohen Arazi]

My personal feeling is we should have a release right before the hackfest.
So the hackfest sets the path for the next cycle. That could mean moving
the hackfest a couple a bit later too

Add for the second part of the year, I'm not sure yet. I just have the
perception everyone is out in the months we are expected to do the bigger
changes, and we end up doing them close to the release date.

El jue, 1 jun 2023 12:46, Philippe Blouin 
escribió:

> Of course I'm coming with my northern hemisphere perspective, and have no
> horse in the race really as being far from RM, but I always thought those
> dates were the best available.
>
> Seems earlier (04, april) makes it closer to the hackfest you referred.
> Later makes it closer to summer holidays.
>
> Were you considering breaking the equal split in time, having a small and
> a big release each year?  November for the big, and march for the small,
> the hackfest starting the next cycle ?  Thinking outside the box...
>
>
> Philippe Blouin,
> Directeur de la technologie
>
> Tél.  : (833) 465-4276, poste 230
> philippe.blo...@inlibro.com
> inLibro | pour esprit libre | www.inLibro.com
> On 2023-06-01 07:35, Tomas Cohen Arazi wrote:
>
> Hi all. Having served as Release Manager for the project a couple times,
> I'd like to ask y'all to think about the dates we've chosen and have stuck
> to the last few years for our releases.
>
> I know they are somehow aligned with our regular yearly meetings, and one
> each semester. But my experience says:
>
> - We all want to implement things we discuss in the Hackfest, but the
> release is too close. So we either push too late in the cycle, or need to
> cool down our brains/ideas for 'after the release in two months'.
> - The other scenario, which I suffered a lot recently (and will soon) is
> summer holidays in the northern hemisphere: you're all out when we should
> be pushing the riskier things to have enough time to fix things, and we end
> up rushing things... on the last third of the cycle.
>
> I don't have a proposal right now, but wanted to say my perception is the
> dates are not ideal as-is. And hear back from you all.
>
> Cheers!
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
> ___
> Koha-devel mailing 
> listkoha-de...@lists.koha-community.orghttps://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/
>
>
___
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/

Re: [Koha-devel] A case against our release dates

[Philippe Blouin]

Of course I'm coming with my northern hemisphere perspective, and have 
no horse in the race really as being far from RM, but I always thought 
those dates were the best available.


Seems earlier (04, april) makes it closer to the hackfest you referred.  
Later makes it closer to summer holidays.


Were you considering breaking the equal split in time, having a small 
and a big release each year?  November for the big, and march for the 
small, the hackfest starting the next cycle ? Thinking outside the box...



Philippe Blouin,
Directeur de la technologie

Tél.  : (833) 465-4276, poste 230
philippe.blo...@inlibro.com

inLibro | pour esprit libre | www.inLibro.com 
On 2023-06-01 07:35, Tomas Cohen Arazi wrote:
Hi all. Having served as Release Manager for the project a couple 
times, I'd like to ask y'all to think about the dates we've chosen and 
have stuck to the last few years for our releases.


I know they are somehow aligned with our regular yearly meetings, and 
one each semester. But my experience says:


- We all want to implement things we discuss in the Hackfest, but the 
release is too close. So we either push too late in the cycle, or need 
to cool down our brains/ideas for 'after the release in two months'.
- The other scenario, which I suffered a lot recently (and will soon) 
is summer holidays in the northern hemisphere: you're all out when we 
should be pushing the riskier things to have enough time to fix 
things, and we end up rushing things... on the last third of the cycle.


I don't have a proposal right now, but wanted to say my perception is 
the dates are not ideal as-is. And hear back from you all.


Cheers!

--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F

___
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/___
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/

[Koha-devel] A case against our release dates

[Tomas Cohen Arazi]

Hi all. Having served as Release Manager for the project a couple times,
I'd like to ask y'all to think about the dates we've chosen and have stuck
to the last few years for our releases.

I know they are somehow aligned with our regular yearly meetings, and one
each semester. But my experience says:

- We all want to implement things we discuss in the Hackfest, but the
release is too close. So we either push too late in the cycle, or need to
cool down our brains/ideas for 'after the release in two months'.
- The other scenario, which I suffered a lot recently (and will soon) is
summer holidays in the northern hemisphere: you're all out when we should
be pushing the riskier things to have enough time to fix things, and we end
up rushing things... on the last third of the cycle.

I don't have a proposal right now, but wanted to say my perception is the
dates are not ideal as-is. And hear back from you all.

Cheers!

-- 
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
___
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/

Re: [Koha-devel] Koha 23.05 released

[Field, Jonathan]

Great work Tomas (and ALL the team who have been involved in this!).
Appreciate it is a huge amount of work for you so we thank you.
Lots to be excited about in this release!
Jonathan

On Wed, 31 May 2023 at 20:50, Tomas Cohen Arazi 
wrote:

> The Koha community is proud to announce the release of Koha 23.05.00.
>
> Koha 23.05.00 is a major release, that comes with many new features.
>
> It includes 26 new features, 145 enhancements, 701 bugfixes.
>
> The full release notes are available here:
> https://koha-community.org/koha-23-05-released/
>
> Debian packages should be available soon
>
> Best regards
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
> ___
> 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/
>


-- 

Jonathan Field

Managing Director

PTFS Europe

[image: Phone icon] M: +44 7919 372002 | T: +44 1483 378728 ext. 1000

[image: Email icon] jonathan.fi...@ptfs-europe.com

[image: Link icon] www.ptfs-europe.com

[image: Click to open Twitter]  [image:
Click to open YouTube] 

[image: Click to open PTFS Europe webpage] 
___
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/

Re: [Koha-devel] Koha 23.05 released

[Marcel de Rooy]

Really great, Tomas. Thanks!


Van: Koha-devel  namens Tomas 
Cohen Arazi 
Verzonden: woensdag 31 mei 2023 21:49
Aan: koha-devel 
Onderwerp: [Koha-devel] Koha 23.05 released

The Koha community is proud to announce the release of Koha 23.05.00.

Koha 23.05.00 is a major release, that comes with many new features.

It includes 26 new features, 145 enhancements, 701 bugfixes.

The full release notes are available here:
https://koha-community.org/koha-23-05-released/

Debian packages should be available soon

Best regards

--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
___
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/