Nicola Ken Barozzi wrote:
Peter Donald wrote:On Thu, 24 Oct 2002 12:41, Berin Loritsch wrote:Should we have a "dead" directory, and move the dead projects there before deleting? In this case, we would have: jakarta-avalon-excalibur/dead/collections The build file would still work, but no wasted effort will be used to maintain the collections. Would that be sufficient?
I would prefer to leave it as is. Theres no real need to separate out the code. The deprecation warnings say it all. Maybe we could add an extra WARNING.txt file to base directory but that should be it.
We don't separate out stable/alpha stuff so I don't see any need to separate out graveyard stuff and I would thing that quite a few people would still object if we did it to ECM
When a project is dead, that means some months from now, IMHO it would be ok just to delete all the files in collections, thus nudging them to the Attic, adding a Warning and redirecting downloads to a CVS tarball in the distributions
avalon-collections-mummified.tar.gz
I see people get confused when "dead" code is left there in CVS.
Agreed - getting a grip on the status of different Excalibur projects is really difficult. Seperating out dead content is a positive move.
Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
