Looking at updater/updatedatabase, it looks like a real mess.... Especially if we think about all the big advances we shall make with the next version , would it be called 2.4 or 3.0 ;)))). So we propose that we could assume that from now on, in head version updater should take on the evolution from version 2.2 to 3.0 and give up all the evolution from 1.2 to 2.2 which would make it too big and too messy to be really maintainable. If nobody needs such a big file any longer, we shall change it. Thanks. -- Henri-Damien LAURENT
Henri-Damien LAURENT <laurenthdl@alinto.com> wrote:
So we propose that we could assume that from now on, in head version updater should take on the evolution from version 2.2 to 3.0 and give up all the evolution from 1.2 to 2.2 which would make it too big and too messy to be really maintainable.
It seems like a good idea to me. The 2.2 updater will still be available from some sourceforge incantation for the forseeable future and I don't think upgrading 1.2 -> 2.2 has been recommended. If this is agreed, I will update the installer to support version checking as needed. Could it happen at an installer/ upgrader IRC meeting? Who wants to be at this meeting and what times around 2005-07-04 and -05 are good (UTC/GMT please)? -- MJ Ray (slef), K. Lynn, England, email see http://mjr.towers.org.uk/ http://www.ttllp.co.uk/koha/
participants (2)
-
Henri-Damien LAURENT -
MJ Ray