Hi Folks
Jonathan and I are planning to use an bug/issue tracker for the
koha-qa.pl tool
We thought it would be a good idea to get some opinions from other Koha
developers, on which tracker to use
here is the list we currently have...
1/ use github.com
2/ use gitlab.com
3/ use a KC.org gitla
Gitlab, please!
On 29/09/15 09:43, Mason James wrote:
> Hi Folks
>
> Jonathan and I are planning to use an bug/issue tracker for the
> koha-qa.pl tool
> We thought it would be a good idea to get some opinions from other
> Koha developers, on which tracker to use
>
> here is the list we currently h
We hate Ruby!
2015-09-28 18:05 GMT-03:00 Liz Rea :
> Gitlab, please!
>
> On 29/09/15 09:43, Mason James wrote:
> > Hi Folks
> >
> > Jonathan and I are planning to use an bug/issue tracker for the
> > koha-qa.pl tool
> > We thought it would be a good idea to get some opinions from other
> > Koha d
Hi,
there is a somewhat hidden feature you could use, described on bug 7045:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7045
If you add 'user' as the default value for a subfield in your
bibliographic frameworks, the field will be automatically filled with
the staff user's surname.
I'd vote 4) - mostly for the reason of 'not yet another account
somewhere' and to have all things Koha in one place.
Am 28.09.2015 um 22:43 schrieb Mason James:
> Hi Folks
>
> Jonathan and I are planning to use an bug/issue tracker for the
> koha-qa.pl tool
> We thought it would be a good idea to
+1 fot github.com or gitlab.com
2015-09-28 17:43 GMT-03:00 Mason James :
> Hi Folks
>
> Jonathan and I are planning to use an bug/issue tracker for the koha-qa.pl
> tool
> We thought it would be a good idea to get some opinions from other Koha
> developers, on which tracker to use
>
> here is the
On Tue, Sep 29, 2015 at 3:01 AM, Katrin Fischer
wrote:
> I'd vote 4) - mostly for the reason of 'not yet another account
> somewhere' and to have all things Koha in one place.
+1 for that
--
Indranil Das Gupta
Phone : +91-98300-20971
Blog: http://indradg.randomink.org/blog
IRC :
Hi all:
I just noticed that we don't actually have a rule against using experimental
features (e.g. smartmatch ~~, given/when) in the coding guidelines. We
impose this rule during the testing/QA process, but it's not actually
documented.
What do we need to do to add a rule? Bring this up a
Hi again:
I also noticed there's no rule forbidding subroutine definitions in PL
scripts. I thought that we had a rule against that as well.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St, Ultimo, NSW 2007
From: David Cook [mailto:dc...@prosentient.com.au]
Sent: T
Hi Katrin,
I tested as well on some subfields, it worked fine with 'user'.
Bug 7045 mentions more replaceable strings: , MM and DD
I successfully tested with 'user DD-MM-', resulting in something like:
testuser 29-09-2015
However I do not find any documentation about the replaceable str
I vote for 4) - for the same reason.
Am 28.09.2015 um 23:31 schrieb Katrin Fischer:
> I'd vote 4) - mostly for the reason of 'not yet another account
> somewhere' and to have all things Koha in one place.
>
> Am 28.09.2015 um 22:43 schrieb Mason James:
>> Hi Folks
>>
>> Jonathan and I are plannin
11 matches
Mail list logo
