#45 hop release apply is incorrect

[Brad Dompe]

We did a "hop release apply <release>", to try it out. A
certain amount of code was checked out, but the hop
database was only updated to indicated all changes in
that current release were applied.

ie. We have release1, release2, releasee3, release4,
release4.1, release42

Doing "hop release apply release42" checked out a
schwack of code, but only marked changes listed as
being in release42 as being applied. The person did not
investigate what version of code they had, so the bug is
either:
- All the code is being checked out, but hop is not
updating the applied change numbers correctly.
Or:
- Hop is updating the applied change number correclty,
and only the code modified since the previous release is
being checked out. If this is the case, there should be a
prereq system to require the user apply the previous
releases. Also, I'd request a hop release apply that
would get everything up to that release, to avoid having
to do it multiple times.