If this is an offer to sponsor the maintenance of a LTS release
(with money or labour), such a version once in a while could be
interesting to some. There might be support firms that can offer
such a paid service. You can find a list on
http://www.koha-community.org/
I don't see why every big Koha
What about LTS (Long Term Support) release in every six months?
Dr. Parthasarathi MukhopadhyayLecturer (Sr. Scale)Department of Library and Information ScienceThe University of Burdwan (WB)--At 5 Dec 2011
On 05/12/2011, at 10:30 , Owen Leonard wrote:
> On Sat, Dec 3, 2011 at 7:34 PM, Mason James wrote:
>>
>> On 2011-12-2, at 2:31 AM, Owen Leonard wrote:
>>
Screw them. If that's the only reason, let's skip to 5.8 for the
next release, or append ".not-a-LibLime-fake" to ours. But do w
Den 05. des. 2011 22:05, skrev Chris Nighswonger:
> 2011/12/5 Mason James :
>>
>> theres a very impressive list of them on wikipedia
>> http://en.wikipedia.org/wiki/List_of_culinary_fruits
>
> We could also use astronomical names of stars, constellations, etc.
If by names: Why not famous book tit
2011/12/5 Mason James :
>
> theres a very impressive list of them on wikipedia
> http://en.wikipedia.org/wiki/List_of_culinary_fruits
We could also use astronomical names of stars, constellations, etc.
Kind Regards,
Chris
___
Koha-devel mailing list
Koh
On 2011-12-6, at 9:34 AM, Mirko wrote:
> Mason James schrieb am 05.12.2011 13:51:05
>
>>
>> ok, so make a better suggestion.
>>
>> how about vegetables? (asparagus, broccoli, carrot, etc...)
>>
>
> puredyne[1] seems to be using something in that direction with names
> like "leek and potato
Mason James schrieb am 05.12.2011 13:51:05
>
> ok, so make a better suggestion.
>
> how about vegetables? (asparagus, broccoli, carrot, etc...)
>
puredyne[1] seems to be using something in that direction with names
like "leek and potato" and "carrot and coriander".
Personally, I like the "s
On 2011-12-5, at 3:44 PM, Jared Camins-Esakov wrote:
> It seems to me that my input is called for here.
>
> > If we're going to be this silly, I'd go with Cait's sweets idea
> > modified for the appropriate nationality of the KohaCon host for the year
> > the release is out.
> >>
> >> my
It seems to me that my input is called for here.
> > If we're going to be this silly, I'd go with Cait's sweets idea
> modified for the appropriate nationality of the KohaCon host for the year
> the release is out.
> >>
> >> my favorite (other than any food category) is important librarians,
On 2011-12-5, at 2:07 PM, BWS Johnson wrote:
>
> Salvete!
>
>>> how about vegetables? (asparagus, broccoli, carrot, etc...)
>>
>
> If we're going to be this silly, I'd go with Cait's sweets idea modified
> for the appropriate nationality of the KohaCon host for the year the release
> is
On Sat, Dec 3, 2011 at 7:34 PM, Mason James wrote:
>
> On 2011-12-2, at 2:31 AM, Owen Leonard wrote:
>
>>> Screw them. If that's the only reason, let's skip to 5.8 for the
>>> next release, or append ".not-a-LibLime-fake" to ours. But do we
>>> want to let them interfere with the real project in
Salvete!
>> how about vegetables? (asparagus, broccoli, carrot, etc...)
>
If we're going to be this silly, I'd go with Cait's sweets idea modified
for the appropriate nationality of the KohaCon host for the year the release is
out.
>
> my favorite (other than any food category) is im
On 2011-12-5, at 1:51 PM, Mason James wrote:
>
> On 2011-12-5, at 10:32 AM, Mirko wrote:
>
>> Mason James schrieb am 05.12.2011 09:10:26
>>>
>>> both android and ubuntu choose their release names in
>>> alphabetical sequence, (like a,b,c,d) as a workaround to your
>>> problem
>>>
>>> ...we co
On 2011-12-5, at 10:32 AM, Mirko wrote:
> Mason James schrieb am 05.12.2011 09:10:26
>>
>> both android and ubuntu choose their release names in
>> alphabetical sequence, (like a,b,c,d) as a workaround to your
>> problem
>>
>> ...we could do that too?, (eg: brie, cheddar, durrus)
>>
>
> Pleas
Mason James schrieb am 05.12.2011 09:10:26
>
> both android and ubuntu choose their release names in
> alphabetical sequence, (like a,b,c,d) as a workaround to your
> problem
>
> ...we could do that too?, (eg: brie, cheddar, durrus)
>
Please don't do this. There are so many nice things in the w
On 2011-12-5, at 12:56 AM, MJ Ray wrote:
> Mason James
>> we could also consider switching to the Debian style?, i have found it quite
>> easy to understand.
>> would it work well for Koha?
>>
>>
>> the Debian project uses both an internal 'linux-kernal' style numbering
>> system (like Koha
Mason James
> we could also consider switching to the Debian style?, i have found it quite
> easy to understand.
> would it work well for Koha?
>
>
> the Debian project uses both an internal 'linux-kernal' style numbering
> system (like Koha does already) and people-friendly nick-names too...
Op 04-12-11 15:04, Mason James schreef:
>>> Katrin failed to mention her excellent counter-proposal to Ian's suggestion
>>> of cheese as a theme: cookies and other sweets as the theme. Koha 3.8
>>> Curried coconut oatmeal chocolate chip cookies, etc.
Been done, kinda. I have Android devices runn
On 2011-12-4, at 1:43 PM, Mason James wrote:
>
> On 2011-12-2, at 4:31 AM, Jared Camins-Esakov wrote:
>
>> Katrin failed to mention her excellent counter-proposal to Ian's suggestion
>> of cheese as a theme: cookies and other sweets as the theme. Koha 3.8
>> Curried coconut oatmeal chocolate
On 2011-12-2, at 4:31 AM, Jared Camins-Esakov wrote:
> Katrin failed to mention her excellent counter-proposal to Ian's suggestion
> of cheese as a theme: cookies and other sweets as the theme. Koha 3.8 Curried
> coconut oatmeal chocolate chip cookies, etc.
>
> Regards,
> Jared
any type of fo
On 2011-12-2, at 2:31 AM, Owen Leonard wrote:
>> Screw them. If that's the only reason, let's skip to 5.8 for the
>> next release, or append ".not-a-LibLime-fake" to ours. But do we
>> want to let them interfere with the real project in yet another way?
>
> I strongly agree with this.
yeah, i
2011/12/1 Ian Walls :
> About your first suggestion (the one you didn't want to get buried in the
> discussion of part 2):
>
> DB revs need to maintain a sequence, as sometimes order of application is
> important. But if two completely orthogonal things are applied out of
> sequence, it really
ehalf Of Ian Walls
> Sent: Thursday, December 01, 2011 1:46 PM
> To: MJ Ray
> Cc: koha-devel@lists.koha-community.org
> Subject: Re: [Koha-devel] Version numbering, starting a discussion
>
> The way I've seen version numbering is in 4 parts:
>
> ...
>
> Major versi
ity.org [mailto:
> koha-devel-boun...@lists.koha-community.org] On Behalf Of Ian Walls
> Sent: Thursday, December 01, 2011 1:46 PM
> To: MJ Ray
> Cc: koha-devel@lists.koha-community.org
> Subject: Re: [Koha-devel] Version numbering, starting a discussion
>
> The way I've
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Ian Walls
Sent: Thursday, December 01, 2011 1:46 PM
To: MJ Ray
Cc: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Version numbering, starting a discussion
The way I've seen version numbering is in 4 parts:
...
> Screw them. If that's the only reason, let's skip to 5.8 for the
> next release, or append ".not-a-LibLime-fake" to ours. But do we
> want to let them interfere with the real project in yet another way?
I strongly agree with this.
-- Owen
--
Web Developer
Athens County Public Libraries
ht
The way I've seen version numbering is in 4 parts:
...
Major version has at yet been a single digit, but should we get up to major
version 9, we'll probably just roll on to 10. It only changes when there
are significant reworkings to the internal mechanisms of Koha.
Major release is two digits,
Paul Poulain
> === DB update numbering === [...]
> What do you think of this idea ? Why should we keep the previous
> numbering scheme ? Any other suggestion ?
It doesn't really matter, so go with whatever's easiest to manage,
but if you go back to plain numbers, I suggest starting from 4 so
that
On 1 December 2011 21:11, Paul Poulain wrote:
> Hello,
>
> There are 2 questions in this mail:
> === DB update numbering ===
> The bug 7167 will probably pushed in a few days, and it's a new way to
> handle updatedatabase. They will be non-linear, meaning update 1 can be
> applied after update 2,
Hello,
There are 2 questions in this mail:
=== DB update numbering ===
The bug 7167 will probably pushed in a few days, and it's a new way to
handle updatedatabase. They will be non-linear, meaning update 1 can be
applied after update 2, and before update 3.
The previous numbering pattern, made fr
30 matches
Mail list logo
