commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mattias J <mjsl...@expertsystem.se>
Subject Re: moving code from sandbox to proper - best practice?
Date Fri, 13 May 2005 08:14:45 GMT
I think I agree with this. I believe it is better to remove the entire 
sandbox directory, so that people notice it has moved (the website says 
where) and can change the SVN repository in use (that can be done; can't it?).

At 2005-05-13 10:10, you wrote:
>I disagree, README is just clutter and should be removed.
>We send out announcements on the mailing list and if people miss that they 
>can look at the website.
>The complete list of components if on the commons homepage so with one 
>click you have a full overview.
>
>-- Dirk
>
>Rory Winston wrote:
>>Good question. We did look at doing a sandbox cleanup when it was 
>>migrated from CVS to SVN. I remember doing a list of dead projects that 
>>were still in sandbox. However, I agree that having a sandbox/{project} 
>>dir with at the very least a README pointing to the new location (for 
>>promoted components) would be useful.
>>
>>
>>skitching@apache.org wrote:
>>
>>>Hi,
>>>
>>>The "moving from sandbox to proper" wiki page needs updating, as it is
>>>all CVS based.
>>>
>>>
>>>http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper
>>>
>>>The main question that needs resolving is:
>>>* should the code be MOVED from sandbox to proper, or COPIED?
>>>
>>>Moving the code means that links to the old location break. But copying
>>>the code means that links to the old stuff don't give any indication
>>>that the main development is now happening elsewhere.
>>>What do people think the best practice is for sandbox->proper promotion?
>>>
>>>I think my preference would be
>>>* move the existing code to {proj}/tags/sandbox
>>>* copy to {proj}/trunk
>>>* create a new sandbox/{proj} directory, containing just a README
>>>   that points to the new project.
>>>
>>>That way, all the sandbox code vanishes from its old location, avoiding
>>>any confusion. But users of the sandbox stuff at least get a hint where
>>>the new stuff is.
>>>
>>>The main disadvantage is clutter left in the sandbox directory.
>>>
>>>
>>>Thoughts?
>>>
>>>Regards,
>>>
>>>Simon
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message