We talked about this on IRC today and decided to worry about that with the next release since we're so close to release right now and I need to get this done. There is more than the version to think about - there is the language as well. And when the version is a dev version we need to link to the next manual - which may or may not be ready yet. There is too much to discuss right now and I need to get this done this week due to my work schedule.
Also - I need to review every help file anyway to see if there are differences that need to be added - so updating the link takes me no time at all. Nicole On Wed, Mar 27, 2013 at 8:45 PM, Robin Sheat <[email protected]> wrote: > Bernardo Gonzalez Kriegel schreef op wo 27-03-2013 om 21:29 [-0300]: > > I was thinking the same thing. Perhaps a syspref with Koha version > > (not the database one) > > > No, Koha knows what version it is. All it needs is to populate a > variable by default that goes into the templates, and then you can go > and stick [% major_minor_version %] (or whatever) in there. > > -- > Robin Sheat > Catalyst IT Ltd. > ✆ +64 4 803 2204 > GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D > > _______________________________________________ > Koha-devel mailing list > [email protected] > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ >
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
