Skip to content

Better mechanism for version upgrade #9

Description

@pranavcode

Every insilico update releases the source as a bundle with no mechanism for programmers using older version to upgrade to the newer version.

The common way followed is the manual movement of sources from older version to newer version.

I can see few problems in this process:

  • Inconsistent file structure across versions can cause failure to upgrade
  • Manual processes are seldom time consuming, errorneous and panicky
  • One is afraid of breaking the working code from older version by upgrading it to newer version, which makes one to stick to working older version

I propose a safe automated update script that can migrate the user to the newer version with her own sources safely, accurately and with minimal manual effort.

I consider this vital and so raising this as an issue (as per version 0.21).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions