Version Progression

At any given time the distribution site will provide access to three different releases of the code, the old, the current, and the new. The old and the current versions are frozen, and changes are made to the new version following the procedures given below. When the accumulated changes merit it a new release will occur. At this point the old is archived, and the new becomes the current. There will follow a short period ($\approx$2 weeks) for fixing bugs which show up, and then the current will be frozen and copied into the new. The procedure then repeats (and repeats and repeats and repeats......).