Hello koha-devel,
Throwing the question : after version 3.10, we're about to release 3.12,
the next version is expected to be 3.14
My question is a small one : what does the "3." mean for us ?
The 3.12 is really different from 3.0, that has been released 5 years
ago. Remembering history, we switc
>From what I've I've heard around the water cooler, we won't be switching to
4.x until there is some major change to the internal infrastructure of Koha
( like Solr support, or perhaps DBIx::Class support ).
I think if were to ditch the traditional versioning system, that maybe the
Ubuntu year/mon
Hello
If you want a librarian point of view, Koha 4 should have a major
visible improvement for librarians and patrons, not only a change in
infrastructure.
And the main improvement we are waiting for is SolR.
I don't even know what is DBIx::Class ;-)
Mathieu
Kyle Hall a écrit :
From what I'
Kyle wrote:
> I think if were to ditch the traditional versioning system, that maybe the
> Ubuntu year/month style would. So a major release this month would be
> version 13.04. I'm not endorsing it, it's just a possibility ; )
If we go that way, please don't use the point as the divider because h
;
>
>
> Today's Topics:
>
> 1. Koha numbering (Paul Poulain)
>
>
> --
>
> Message: 1
> Date: Fri, 05 Apr 2013 09:40:22 +0200
> From: Paul Poulain
> To: Koha Devel
> Subject: [Koha-devel] Koha numbering
> Message-ID: <5
On Fri, Apr 5, 2013 at 3:40 AM, Paul Poulain wrote:
> What could/should we expect to decide to switch to 4.x ?
>
IIRC this was discussed sometime back on irc/wiki/mailing list/somewhere
and the prevailing thought was that 4.x would happen when the solr
implementation was stable. But then my memor
Le 05/04/2013 13:34, Kyle Hall a écrit :
> From what I've I've heard around the water cooler, we won't be switching
> to 4.x until there is some major change to the internal infrastructure
> of Koha ( like Solr support, or perhaps DBIx::Class support ).
The switch from 2.x to 3.x was driven by a fu
Le 05/04/2013 14:11, Chris Nighswonger a écrit :
> It seems that any "major" move forward would qualify for a major version
> increment, however. Something like DBIx, the completion of the move from
> C4:: to Koha::, the completion of the move from YUI to bootstrap, etc.
In this case, we could have
On Fri, Apr 5, 2013 at 9:26 AM, Paul Poulain wrote:
> As we have each 6 month a new major release, why not increment the major
> number on each of them ?
> And as we're about to release 3.12.0, my preference is slowly moving
> toward *removing* the 3. and saying each major release get it's major
>
I was not aware of that. I have no strong opinion on the matter in general,
but I will say that with this style of versioning at least we wouldn't have
to argue over what constitutes and justifies a major revision number change
; )
Kyle
http://www.kylehall.info
ByWater Solutions ( http://bywaters
On Fri, Apr 05, 2013 at 03:26:27PM +0200, Paul Poulain wrote:
> And as we're about to release 3.12.0, my preference is slowly moving
> toward *removing* the 3. and saying each major release get it's major
> number. So 12.0, 12.1, 12.2,... then 14.0,...
>
The 3.xx releases have been so succesfull t
At 07:34 AM 4/5/2013 -0400, Kyle Hall wrote:
From what I've I've heard around the water cooler, we won't be switching to
4.x until there is some major change to the internal infrastructure of Koha
( like Solr support, or perhaps DBIx::Class support ).
I think if were to ditch the traditional ver
Le 05/04/2013 15:26, Paul Poulain a écrit :
> So 12.0, 12.1, 12.2,... then 14.0,...
Another positive aspect of this option : 12.0 IS a number.
3.12.0 isn't ;-)
--
Paul POULAIN - BibLibre
http://www.biblibre.com
Free & Open Source Softwares for libraries
Koha, Drupal, Piwik, Jasper
__
I think you have some good ideas here. It seems to me that support for each
release drops off rather dramatically. Our oldest supported release is
currently 3.8 which was first released about 1 year ago!
Right now I believe a release is only supported as long as we have a
maintainer willing to do
Salvete!
You silly, silly man. Everyone knows that anything past nine isn't
real maths. ;)
xkcd.com/899/
I still mostly don't care how things are numbered. I care far more
that thongs operate how they ought to.
Cheers,
Brooke___
Koha-devel
I'm not too pick about the numbering, as a trainer I have been saying that
we'll roll to 4.0 when we get Solr since that's what was said at KohaCon
and in IRC meetings (maybe on the mailing list too). I think a single
number is certainly easier for the average person than our current 3.10.4
type s
> I'm not too pick about the numbering, as a trainer I have been saying that
> we'll roll to 4.0 when we get Solr since that's what was said at KohaCon
> and in IRC meetings (maybe on the mailing list too). I think a single
> number is certainly easier for the average person than our current 3.10.
On 6 April 2013 07:10, Jared Camins-Esakov wrote:
>
>> I'm not too pick about the numbering, as a trainer I have been saying that
>> we'll roll to 4.0 when we get Solr since that's what was said at KohaCon and
>> in IRC meetings (maybe on the mailing list too). I think a single number is
>> certa
Hi,
On Fri, Apr 5, 2013 at 12:40 AM, Paul Poulain wrote:
> Another option I see could be to remove the "3." and name version 12.0,
> 12.1, 12.2, 14.0, 14.1,... (that would be fine for the current
> updatedatabase mechanism)
I don't ask much of version number schemes. Really just two things:
fir
On Fri, Apr 5, 2013 at 2:28 PM, Galen Charlton wrote:
> Consequently, I'd be happy if we kept the 3.x series going
> indefinitely, or if we bumped up the major version number when it felt
> right, or if we dropped the "3." and called the fall release 13.0 or
> 14.0.
>
> Whatever gets decided, I *
I too was looking forward to 3.14. I'm happy to change it after that.
:P
Yes, ok, it's a sentimental thing but... it's PI. COME ON.
Liz
On Sat, Apr 6, 2013 at 9:48 AM, Nicole Engard wrote:
> On Fri, Apr 5, 2013 at 2:28 PM, Galen Charlton wrote:
>
>> Consequently, I'd be happy if we kept the
On Fri, Apr 5, 2013 at 6:45 PM, Liz Rea wrote:
> I too was looking forward to 3.14. I'm happy to change it after that.
>
> :P
>
> Yes, ok, it's a sentimental thing but... it's PI. COME ON.
>
>
So does that make for a potentially irrational release?
Chris
_
From: Liz Rea
Sent: Friday, April 05, 2013 6:45 PM
To: Nicole Engard
Cc: Koha Devel
Subject: Re: [Koha-devel] Koha numbering
> I too was looking forward to 3.14. I'm happy to change it after that.
> :P
> Yes, ok, it's a sentimental thing but... it's PI. COME ON.
It’s
Means we never need to worry about increasing the major number again, just keep
adding digits.
:)
Chris
Christopher Nighswonger wrote:
>On Fri, Apr 5, 2013 at 6:45 PM, Liz Rea wrote:
>
>> I too was looking forward to 3.14. I'm happy to change it after that.
>>
>> :P
>>
>> Yes, ok, it's a
At 03:37 PM 4/6/2013 +1300, Chris Cormack wrote:
Means we never need to worry about increasing the major number again, just
keep adding digits.
:)
Chris
Christopher Nighswonger wrote:
On Fri, Apr 5, 2013 at 6:45 PM, Liz Rea wrote:
I too was looking forward to 3.14. I'm happy to change it afte
Le 05/04/2013 20:28, Galen Charlton a écrit :
> I don't ask much of version number schemes. Really just two things:
> first, that they increase from version to version. Second, that we
> don't spend a great deal of time discussing them. :)
OK, I propose to open a poll to have as many ppl opinion
Paul,
OK, I propose to open a poll to have as many ppl opinion as possible.
> The most interested ppl being users/libraries themselves !
>
Are you seriously proposing we waste MORE time on this? As everyone
involved in this discussion has expressed a willingness to start versioning
Koha with whol
At 12:15 AM 4/7/2013 +0200, Paul Poulain wrote:
[snip]
The poll would have the following options :
* keep 3. "forever"
* keep the 3. until a major functional change is made, like introducing
a new search engine. The numbering change is decided by the Release Manager.
* drop the 3. and use 14.0
Paul wrote:
>At 12:15 AM 4/7/2013 +0200, Paul Poulain wrote:
>[snip]
>>The poll would have the following options :
>> * keep 3. "forever"
>> * keep the 3. until a major functional change is made, like
>introducing
>>a new search engine. The numbering change is decided by the Release
>Manager.
Hello
Maybe you will not agree with me, but here is my *personal *opinion
about release rythm : 6 month between each "major" release seems quite a
short delay.
In France we have libraries using 3.10 (I think only my library for the
moment), 3.8, probably 3.6, 3.2 (with a lot of local changes).
On 7 April 2013 20:27, Mathieu Saby wrote:
> Hello
> Maybe you will not agree with me, but here is my personal opinion about
> release rythm : 6 month between each "major" release seems quite a short
> delay.
> In France we have libraries using 3.10 (I think only my library for the
> moment), 3.8,
Hi Mathieu,
you are right in that updating every half year is a lot of work, but the
good thing is, that you don't have to. We have libraries that are still
on 3.6.x now and we will probably update them directly to 3.12 sometime
this year.
The positive side on half year feature releases is that y
oha-devel-boun...@lists.koha-community.org
[koha-devel-boun...@lists.koha-community.org] namens Katrin Fischer
[katrin.fischer...@web.de]
Verzonden: zondag 7 april 2013 10:48
To: koha-devel@lists.koha-community.org
Onderwerp: Re: [Koha-devel] Koha numbering
Hi Mathieu,
you are right in that updat
I think this is a worthwhile discussion to have, and I'm actually in
no hurry (yet) to cut it off. I think there are still aspects which
need to be considered.
Version numbering is important to different groups for different
reasons. For developers, we need version numbering to keep track of
where
> But please do not jump from 3 to 14 !
>
Good point. I added the following proposal to the agenda for the next IRC
meeting:
* Vote on (NOT DISCUSS) the proposal to increment the major version for
every feature release starting after version 3.14, which is due to be
released on November 22, 2013
Salvete!
Thank you for that, Jared.
Hopefully my mail won't be ate. When the initial thread started, I
didn't really care. At this point, I feel like the spirit of the
discussion has shifted from pure numbering to the development release cycle. I
also am a little torn on the large nu
At 04:07 PM 4/7/2013 -0400, Jared Camins-Esakov wrote:
But please do not jump from 3 to 14 !
Good point. I added the following proposal to the agenda for the next IRC
meeting:
When does the vote take place, and how does one join in? I've no
experience whatsoever with "IRC", what's needed
At 04:07 PM 4/7/2013 -0400, Jared Camins-Esakov wrote:
But please do not jump from 3 to 14 !
Good point. I added the following proposal to the agenda for the next IRC
meeting:
When does the vote take place, and how does one join in? I've no
experience whatsoever with "IRC", what's needed
http://koha-community.org/get-involved/irc/ may be the resource you are
looking for.
Cheers,
Liz Rea
On 08/04/13 10:07, Paul wrote:
> At 04:07 PM 4/7/2013 -0400, Jared Camins-Esakov wrote:
>
>> But please do not jump from 3 to 14 !
>>
>>
>> Good point. I added the following proposal to the ag
Thank you for Katrin & Chris for your answers ( I also read some
comments on irc...)
You convinced me, 1 year release would be a bad idea ;-)
Mathieu
Le 07/04/2013 10:48, Katrin Fischer a écrit :
Hi Mathieu,
you are right in that updating every half year is a lot of work, but the
good thing
On 8 April 2013 10:43, Mathieu Saby wrote:
> Thank you for Katrin & Chris for your answers ( I also read some comments on
> irc...)
> You convinced me, 1 year release would be a bad idea ;-)
>
Perhaps you read the stats for 3.12.0 on IRC?
For other people it was
771 patches from 59 people in less
Galen Charlton schreef op vr 05-04-2013 om 11:28 [-0700]:
> Really just two things:
> first, that they increase from version to version.
I reserve the right to get grumpy if they don't map cleanly into the
debian versioning scheme.
> Second, that we
> don't spend a great deal of time discussing
ltimo NSW 2007
tel: 02 92120899
fax: 02 92120885
dc...@prosentient.com.au
-Original Message-
Message: 1
Date: Sun, 7 Apr 2013 12:10:30 +
From: Marcel de Rooy
To: "koha-devel@lists.koha-community.org"
Subject: Re: [Koha-devel] Koha numbering
Message-ID:
<80
Yes, lots of patches, and
- it would be difficult to find a RM for 1 year,
- libraries would not be happy if they have to wait 1 year to see their
sponsored devs pushed in master,
- the update from 3.0 to 3.2 (2 years...) seems to be a very very bad
memory for lot of people (I think at that time
Hi,
Not to nitpick, but won't numbering Koha with 4.x open possibilities
of confusion with that other prop. product with a similar sounding
name and version numbering?
just wondering aloud :)
cheers
--
Indranil Das Gupta
Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC
885
dc...@prosentient.com.au
-Original Message-
Message: 1
Date: Sun, 7 Apr 2013 12:10:30 +
From: Marcel de Rooy
To: "koha-devel@lists.koha-community.org"
Subject: Re: [Koha-devel] Koha numbering
Message-ID:
<809BE39CD64BFD4EB9036172EBCCFA310E20641A@S-MA
to decide on a
> goal/trigger to switch to 4.x, and to just continue 3.x until that
> goal/trigger is reached.
>
>
> David Cook
> Systems Librarian
> Prosentient Systems P/L
> ABN 31 078 409 168
> 72/330 Wattle St,
> Ultimo NSW 2007
> tel: 02 921
On Mon, Apr 8, 2013 at 1:02 PM, Ian Walls wrote:
> I'm on the side of moving to Koha 4.0, and then looking into a
> browser-based means of upgrading the system from there. Firefox, Chrome,
> Dokuwiki and most mobile apps do not require any kind of additional process
> to upgrade; you just click
48 matches
Mail list logo
