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
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 a close approximation of
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
_
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 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 *
Hi,
On Thu, Apr 4, 2013 at 11:28 AM, Galen Charlton wrote:
> Tomorrow I will be branching 3.12.x. Bugfixes required for the 3.12.0
> release will be pushed to master first, then cherry-picked for 3.12.x.
I have now branched 3.12.x.
Regards,
Galen
--
Galen Charlton
Manager of Implementation
Eq
Hi Marcel,
On Fri, Apr 5, 2013 at 12:25 AM, Marcel de Rooy
wrote:
> At this moment QA does focus more on the bugfixes.
> Could you let the QA team know when they should start doing regular QA again
> on the enhancements/new features?
I will do so. Please continue to focus on bugfixes.
Regards
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 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
> 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.
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
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
Paul (et.al.),
Maybe this could go into a different thread? I think is off-topic
>
Agreed.
[snip]
> A two year "LTS" cycle, with a further two years "support", plus one more
>> year of "not dropping off the edge of the world" works extremely well as a
>> policy principle, which I feel must be b
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
Maybe this could go into a different thread? I think is off-topic
On Fri, Apr 5, 2013 at 10:32 AM, Paul wrote:
> 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 interna
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
__
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
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
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 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
>
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
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
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
Nice question. I don't know, too. But really, the 3. has important meaning, i
guess! Maybe nicole engard or chris and answer!
Best regards!
Nguyen Quoc Uy
On 05.04.2013, at 14:00, koha-devel-requ...@lists.koha-community.org wrote:
> Send Koha-devel mailing list submissions to
>koha-devel@li
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
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'
>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 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
Galen,
At this moment QA does focus more on the bugfixes.
Could you let the QA team know when they should start doing regular QA again on
the enhancements/new features?
Thanks,
Marcel
Van: koha-devel-boun...@lists.koha-community.org
[koha-devel-boun...@l
Salvete!
Won't matter. Everyone knows that Galen is a bot. *duck*
Cheers,
Brooke___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.o
Le 05/04/2013 00:14, Brendan Gallagher a écrit :
> Jesse Weaver, the 54th committer to Koha, will be working with ByWater
> from May 15th to about August 15th of 2013.
>
> He will be dedicated to working only on Koha work, like signing off on
> patches and fixing bugs
Galen, with 2 dev full time
On 4 April 2013 20:53, Chris Cormack wrote:
> So writing WWW::Mechanize tests to test things functions also.
>
> I'd like to build up a set of tests that can simulate an hour in an
> average(ish) library, and have them running after any successful
> jenkins build. I can help with the jenkins side
+1 from me too; the biggest qa team ever and hopefully the smallest queue :)
Van: koha-devel-boun...@lists.koha-community.org
[koha-devel-boun...@lists.koha-community.org] namens Katrin Fischer
[katrin.fischer...@web.de]
Verzonden: vrijdag 5 april 2013 7:
33 matches
Mail list logo
