Page History

...

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.

If you decide to move the CVS directory itself by modifying CVSROOT, make sure you create a backup of the jakarta-commons module before copying, in case something goes wrong.

1. Make sure your component still builds OK by building it in its new home.
   
2. 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 The easiest way to update a mavenized site once you've built and tested it locally is to run

$maven -Dmaven.username=${apache.username} site:sshdeploy

1. Update the commons web site to reflect your component's move. You will need to update the menus under jakarta-commons/xdocs/stylesheetcommons-build/menus (components-items.xml ent and sandbox-items.xmlent), as well as the main more descriptive listings under jakarta-commons/xdocscommons-build/parts (components.xml file-table.ent and sandbox-table.ent).
   
2. Send an announcement to commons-dev and commons-user announcing the move.
   
3. Gather a list of committers for the component, ask pmc@jakarta.apache.org to give them commit access to component in commons-proper.
   
4. Start planning a release
   

...