Date: 2004-05-20T13:42:11
   Editor: RobertBurrellDonkin <[EMAIL PROTECTED]>
   Wiki: Jakarta Commons Wiki
   Page: MovingFromSandboxToProper
   URL: http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProper

   Moved from original wiki

New Page:

This page describes how to move a component from the commons sandbox to the commons 
proper.  This page assumes you're already an Apache committer with karma for both 
jakarta-commons and jakarta-commons-sandbox.  If you don't have karma, ask for it or 
get someone to help you.

 1. Start vote on commons-dev mailing list, stating reason for promotion of the 
component.

 1. After vote passes, send announcement with time of move and remind everyone to have 
any files in the component checked in by that time.

 1. Actual CVS move:

  i. Log in to your Apache cvs account
  i. Checkout jakarta-commons and jakarta-commons-sandbox, and:
{{{
$cd jakarta-commons-sandbox/foo

$cvs import jakarta-commons/foo commons_sandbox commons_promotion
}}}
[the latter two arguments are required by CVS but arbitrary -- read help on cvs import 
for more details]  Also, it will ask you for a commit message.  I couldn't remember 
the vi commands to save (:w) or quit (:q): http://www.vmunix.com/~gabor/vi.html#Partb
{{{
$cd ..

$cvs remove -fR foo

$cd ..

$cvs commit
}}}

That's it for the actual CVS move.  Verify the move succeeded by doing a clean 
checkout of both jakarta-commons and jakarta-commons-sandbox.  Verify that ViewCVS has 
picked up the changes correctly.

 1. Make sure your component still builds OK by building it in its new home.

 1. Update the web site for your component.  Start with maven clean if your site is 
mavenized.  Your site should now be at jakarta.apache.org/commons/foo rather than 
jakarta.apache.org/commons/sandbox/foo

 1. Update the commons web site to reflect your component's move.  You will need to 
update the menus under jakarta-commons/xdocs/stylesheet/menus (components.xml and 
sandbox.xml), as well as the main jakarta-commons/xdocs/components.xml file.

 1. Send an announcement to commons-dev and commons-user announcing the move.

 1. Gather a list of committers for the component, ask [EMAIL PROTECTED] to give them 
commit access to component in commons-proper.

 1. Start planning a release ;)

(Appendix)

 1. Check-out jakarta-site2 and edit jakarta-site2/xdocs/index.xml and news.xml. Put a 
news of "Commons-XX graduated from Sandbox to Commons-Proper"

 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to