Dear Friends,
In my experience Koha installation from Ubuntu packages is very convenient
and easy to keep update with forthcoming versions.
Everything works fine with latest version of Koha.
But one problem still haunting me, change of default time fixed to run
fines.pl cron.
Many users like to c
I sent my message just a moment too soon.
> 3) A detailed test plan. When I say "detailed," I mean that it should
> include enough detail that it could be followed by someone familiar with
> Koha who does not use whatever section of the code you are editing. A test
> plan with forty steps may se
A gentle reminder: if there is information needed for testing a patch, it
should be in your commit message, not just in comments on the bug. If -- in
the course of looking at a patch for pushing to Master -- I follow the test
instructions in a commit message and the patch does not work, or if I can
On Wed, Nov 28, 2012 at 4:37 PM, Chris Cormack wrote:
> Not being part of the QA team, but speaking as Release Maintainer, I
> think this is a great idea. First up people who are from the same
> organisation could comment on the patch, I shouldn't QA this, can
> someone else. If no one does step u
On 29 November 2012 10:34, Katrin Fischer wrote:
> Hi all,
>
> We already agreed some time ago that the patch writer and the patch sign
> offer should not be from the same company/library/party. I would really
> like to extend that rule to also apply for patch writer and QA team
> member. For 3.12
Hi all,
We already agreed some time ago that the patch writer and the patch sign
offer should not be from the same company/library/party. I would really
like to extend that rule to also apply for patch writer and QA team
member. For 3.12 we got a big QA team, which is great, because with all
the o
Sorry, I did not mean to cause any offence here. I thought I am giving a
user feedback to address a bottleneck in the application. Please keep the
hard work and good Luck
Dr Dilan Roshani, Koya University, Kurdistan Region, Iraq,
On Wed, Nov 28, 2012 at 7:58 PM, Jared Camins-Esakov <
jcam...@cpbi
Hello.
Please make sure you guys deal with the Indexing and search tool for non
> Latin characters in Koha. This need to function by default without
> any complications.
>
I appreciate your eagerness, however, list etiquette dictates that you keep
your replies on-list and sign your name. Common c
>
> In which month Koha version 3.12?
>>
>
> Koha is on a six month development cycle, so it will be released in May
> 2012.
>
Sorry, time travel is only permitted for RMs. Everyone else will have to
wait until May 2013.
Regards,
Jared
--
Jared Camins-Esakov
Bibliographer, C & P Bibliography Se
Vimal,
In which month Koha version 3.12?
>
Koha is on a six month development cycle, so it will be released in May
2012.
Regards,
Jared Camins-Esakov
--
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcam...@cpbibliography.com
(web) http:
Dear Friends,
In which month Koha version 3.12?
Regards,
--
Vimal Kumar V.
Mahatma Gandhi University Library
Kottayam, Kerala- 686 560
Web: http://www.vimalkumar.org
Blog: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in
Paul,
> All QA members should already have been accessing the quality of
> > patches at least to the same degree as those doing generic sign-offs and
> > really to a greater degree. So as I say, the burden of '-s' is, indeed,
> > trivial.
> What is not-fun is that for string or really trivial chan
Le 28/11/2012 15:30, Chris Nighswonger a écrit :
> All QA members should already have been accessing the quality of
> patches at least to the same degree as those doing generic sign-offs and
> really to a greater degree. So as I say, the burden of '-s' is, indeed,
> trivial.
What is not-fun is that
Hi Marcel,
My comment was directed at the additional burden presented by adding a '-s'
and not a reflection of my opinion or view of the importances of the duty
of QA. In reality, I'm surprised that this request is even an issue. All QA
members should already have been accessing the quality of pat
The discussion was certainly not meant to be trivial :)
And the sign-off should not be either..
Van: koha-devel-boun...@lists.koha-community.org
[koha-devel-boun...@lists.koha-community.org] namens Chris Nighswonger
[cnighswon...@foundations.edu]
Verzonden: woen
+1 for QA signoffs; it seems a trivial addition.
On Mon, Nov 26, 2012 at 8:52 AM, Jared Camins-Esakov <
jcam...@cpbibliography.com> wrote:
>
> > Until now, we said the QA goal was to be concentrated on code quality,
>> > testing the feature was made 'somewhere else'. (that's why I also think
>>
Well this is what I wanted to do several months ago when I first said I wanted
to do QAA so you know I'm all in.
+1 from me
Travis Elliott Davis
Development Support Specialist
903.571.4257
elli...@bywatersolutions.com
On Nov 27, 2012, at 7:08 PM, Mason James wrote:
>
> On 2012-11-27, at 2
Hi,
I am looking for some feedback on the following. Opened Bugzilla report 9164
for it.
Would it be an idea to separate the Koha password of kohaadmin [or whatever you
name it during installation] from the database password (in terms of security)?
Furthermore, is it necessary that kohaadmin
18 matches
Mail list logo
