Hi,
To add one clarification, since Equinox is not holding any registration
slots for the conference, the "free registration to Code4Lib" will be
done by reimbursing the awardees $150 each for the registration fee.
This reimbursement is in _addition_ to the $750 for travel and
accommodations.
Please excuse the cross-posting.
Equinox Software is offering 2 scholarships to the code4lib conference
in February.
The scholarships will reimburse travel and accommodation expenses up to
$750.00 USD for a full-time employee from public libraries using either
Evergreen or Koha to attend the
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
Paul,
About your first suggestion (the one you didn't want to get buried in the
discussion of part 2):
It would be feasible to employ a new numbers system just for DB revs (not
for releases). DB rev is only really used in master, so the third number
(maintenance release) is always "00".
What w
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
On Thu, Dec 1, 2011 at 10:22 AM, Fischer, Katrin
wrote:
> I think changing our num
I think changing our numbering scheme will only cause more confusion than it
will help. Perhaps we should have an explanation somewhere in the wiki – but
the current numbering is logical and has a lot of important information.
-- Katrin
From: koha-devel-boun...@lists.koha-community.org
[mailt
Hey All,
I just wanted to let everyone know that I've updated my virtual
appliances to 3.6. This is a complete rebuild using Debian 6.0 (
Squeeze ) instead of Lenny. I also added a bit more to the Koha
Console program for automatically fixing the networking issue that
crops up on virtual machines
> 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
12 matches
Mail list logo
