We discussed several times as to how one should act as new versions of DiViMe come out, with changes to the tool selection. We have two paths:
Try to deal with this "for" the newbie user
Provide instructions for the newbie user to do this
1. Deal with updates "for" the user
The procedure would be something like:
upon vagrant up, check for latest release of DiViMe
if release has changed from x.x to x.y, then run a script that removes the contents of the VM and installs new contents
if release has changed from x.x to y.z, then tell the user This version of DiViMe is deprecated. Please do vagrant destroy and vagrant up
2. Have user deal with updates
The procedure would be something like:
upon vagrant up, check for latest release of DiViMe.
OR ask users to sign up for updates via github -- then they get info about new releases over email.
If there is a new release, tell the user There is a newer version of DiViMe. If you want the latest version, please do vagrant destroy and vagrant up. The latter solution involves a waste of time, since it always does complete destroy+reconstruct.
Resolution: We pick option 2: Leave it to the user to decide and implement updates
All things considered, the former would be hard to maintain, and the waste of time may only occur once in a while, and always when the user wants to do it.
We discussed several times as to how one should act as new versions of DiViMe come out, with changes to the tool selection. We have two paths:
1. Deal with updates "for" the user
The procedure would be something like:
This version of DiViMe is deprecated. Please do vagrant destroy and vagrant up
2. Have user deal with updates
The procedure would be something like:
If there is a new release, tell the user
There is a newer version of DiViMe. If you want the latest version, please do vagrant destroy and vagrant up
. The latter solution involves a waste of time, since it always does complete destroy+reconstruct.Resolution: We pick option 2: Leave it to the user to decide and implement updates
All things considered, the former would be hard to maintain, and the waste of time may only occur once in a while, and always when the user wants to do it.