Monthly upgrades to R-Instat

[rdstern]

After @ChrisMarsh82 and @lilyclements visit to Kenya, the plan is for monthly upgrades to R-Instat. This is to prepare the initial release on 20th, which is tested, and the final release is put on the website at the end of the month.
This message documents what happened to the first month of this policy, and suggests the plan for the next release.
I asked what happens if the timetable slips, and was told, it won't! So, if the 20th is missed, then that month would be missed. I write this message on 21st May, and so assume there will not be a release this month.
If I am right, then Version 0.7.6 will be released internally by 20th June, and will be the next release? That timing is "interesting", because we have just finished 2 weeks of using Version 0.7.5 in climatic workshops (Kenya, Ghana). The next is Zimbabwe and will start on 20 June!
So, I chronical the effective testing of Version 0.7.5, partly via the climatic workshops and propose that the Zimbabwe workshop should use the proposed provisional version of 0.7.6?

1. In the Kenya workshop we quickly found 2 problems - missing packages - that were not critical, i.e. users can add missing packages themselves. But it was great that they were added to the released version, used in the Ghana workshop. I assume with a more comprehensive system of testing, there may be more changes in future versions, though I assume minor bug-fixing is not in that category. They are fixed, in the usual way, but for the next release, and only included in the update if they are deemed critical.
2. However, yesterday @fran2or found what I consider to be a critical bug in 0.7.5. The Climatic > Prepare > Start of the Rains dialogue just doesn't work. It is important and they used the only "work-around" that I could also consider, and that is that the dialogue works fine in the previous version, i.e. 0.7.4. There is now a question - once we resolve that bug - what we do with Version 0.7.5. My suggestion is that were this found before the end of the month, then it should be fixed in the released version. But now, we also propose the users keep the previous version, while it is the penultimate version and we don't fix until Version 0.7.6.
3. This solution will not work if we are able to update soon as other packages do, i.e. just update, and not install a whole new version.