excalibur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <pe...@realityforge.org>
Subject Re: Nuke Compatibility
Date Sat, 19 Jun 2004 14:58:19 GMT
Leo Simons wrote:

>> This would entail
>> * Bundling up the current codebase and placing it in public location
>> * Adding some wordage to the excalibur site describing move
>> * Pointing users at replacement codebases
>>   - commons-cli for cli
>>   - commons-collections for collections
>>   - spice-jndikit for naming
>>   - doug leas concurrent for concurrent
>>   - spice-salt for io
>> * removing compatibility from build system
>> * removing compatiblity from subversion
>>
>> Does anyone have a problem with this?
> 
> 
> +1 to the nuking...but I don't like the first bullet nor the last two. 
> Why not just a
> 
> svn copy -m "excalibur-compatibility is put in graveyard mode..." \
> https://svn.apache.org/repos/asf/excalibur/trunk/compatibility \
> https://svn.apache.org/repos/asf/excalibur/tags/Excalibur-Compatibility-Archived 
> 
> 
> svn delete -m "excalibur-compatibility is put in graveyard mode..." \
>   https://svn.apache.org/repos/asf/excalibur/trunk/compatibility

Easier and more consistent with their guidelines to just tag the whole 
repo and then svn rm the compatibility dir. I don't mind skipping the 
first step as less work for me but I just thought it would be easier for 
users.

--
Cheers,

Peter Donald
--------------------------------
  These aren't the droids you're
  looking for. Move along.
--------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Mime
View raw message