Forum OpenACS Development: Re: direct manipulation of CVS repository and shifting packages into /contrib/obsolete-packages

This has also broken all tags made prior to the change. If I (for example) want to bring something up to date that was implemented on oacs-4-6-2-final and perhaps used the old acs-workflow package, and I were to try and use CVS to find a nice small representation of the local changes, I would find that it was impossible because "oacs-4-6-2-final" no longer refers to the same thing it used to, it refers to the old oacs-4-6-2-final except with some of the core packages moved out to the obsolete directory.

This is, in my personal opinion, not acceptable. If the packages affected were all non-core it might be easier to wear, but 3 of them were previously "core", so this will screw people looking (for example) to upgrade from previous versions to OACS5.

Yes, this can be worked around, but we have revision control for a reason.