A general comment on versions, design and architecture changes

[vrms]

@bkm

Nowhere in his community address on version stability did he address the ability to re-install on a fresh server one of the supported legacy versions.

@bkm

So, if the team wants to be really serious about making stable versions for 2, 3, or 4, years, then this has to be part of the process. Just running “bench update” only works when the server has not crashed. The definition of having a stable version MUST include the ability to install that stable version from scratch without being an advanced developer. It has to be as simple as installing the Ubuntu 16.04 LTS.

wouldn’t you just have to do an installation with the v10.x.x branch in order to get a fresh v10 installation?

probably at this point in time it would have to be a manual installation, so you can select the desired branch (or is there a flag that’d work with the install.py script)? I guess these are one of the questions which have to be ironed out (and where also the integrators may be one of the groups that might have a big interest in contributing to such practicalities).

• the erpnext-docker-debian project by @pipech may be an easy way (once one get’s over the hurdle to sufficiently familiarize oneself with using docker) for getting legacy/LTS versions running

• one could get the idea of creating an LXD/LXC image with those legacy/LTS versions which then could be spun up pretty quickly.

I this the possibilities are numerous and we’d just have to focus on one or 2 options and maintain those well. This can be going via Frappe Pvt. or from within the Community (where I could imaging the Foundation could provide infrastructure for hosting images i.e.)

@brian_pond

I agree with @bkm , that this needs to be given more thought/effort.

I think a one deal could be … Frappe Pvt. maintaining the code, the community maintaining the easy installation/deployments schemes (install.py, docker, LXC/LXD image)