We have fully documented the process of adding a syspref to Koha[1].
It remains unclear which workflow syspref deprecation should follow.
I've been told on IRC that, traditionally, deprecated sysprefs are set
to a 'good default' value, and then hidden.
If you take a look at bug 8724 [2] you'll
Hi,
On 09/05/2012 10:50 AM, Tomas Cohen Arazi wrote:
If you take a look at bug 8724 [2] you'll notice that i followed that
path. But as NoZebra is to be fully removed from Koha tree I ask: what
do u think the workflow for syspref removal be? It should be added to
the sysprefs wiki too. I can do
Colin,
Do we need to add an explicit step to ensure that the removal is
included in the release notes of the upstream release?
Or will the commit message from [2] suffice
The list of sysprefs in the release notes is automatically generated. I
will add to the script so that it notes removed
At 11:41 AM 9/5/2012 -0400, Galen Charlton wrote:
On 09/05/2012 10:50 AM, Tomas Cohen Arazi wrote:
If you take a look at bug 8724 [2] you'll notice that i followed that
path. But as NoZebra is to be fully removed from Koha tree I ask: what
do u think the workflow for syspref removal be? It
Apologies - please disregard, didn't put #4 below in context. P.
At 11:41 AM 9/5/2012 -0400, Galen Charlton wrote:
On 09/05/2012 10:50 AM, Tomas Cohen Arazi wrote:
If you take a look at bug 8724 [2] you'll notice that i followed that
path. But as NoZebra is to be fully removed from Koha tree I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 05-09-12 19:08, Paul schreef:
[4] Add an update to updatedatabase.pl deleting the preference
from the systempreferences table.
+1
but from an excess of caution, is there any possibility that this
could complicate a MySQL {dump form earlier
