Page History

...

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

Maybe you have to checkout Checkout commons-build now. You - you can do this by using

$svn co https://svn.apache.org/repos/asf/commons/proper/commons-build/trunk commons-build

on the same level as your project-directory.

1. If you have update your gump.xml and project.xml
   
2. Update the commons web site to reflect your component's move. You will need to update the menus under commons/commons-build/menus (components-items.ent and sandbox-items.ent), as well as the more descriptive listings under commons/commons-build/parts (components-table.ent and sandbox-table.ent).
   
3. Update /www/commons.apache.org/sandbox/.htaccess and add a "Redirect permanent" to have automatic redirection from your projects sandbox to the proper website.
   
4. Send an announcement to dev and user mailing lists announcing the move.
   
5. Gather a list of committers for the component, ask pmc@commonsdev@commons.apache.org to give them commit access to component in commons-proper.
   
6. Start planning a release
   

(Appendix)

1. Check-out jakarta-site
2. edit jakarta-site/news.xml. Put a news of "Commons-XXXX graduated from Sandbox to Commons-Proper"
3. edit jakarta-site/docs/.htaccess and add a "Redirect permanent" to have automatic redirection from your projects sandbox to the proper website. Search for "vfs" to have a template.
   

$svn co https://svn.apache.org/repos/asf/jakarta/site

1. Edit xdocs/site/news.xml
   

And follow docs/README.txt to regenerate the site. Check if it looks good.

1. Create a diff of your changes and ask a PMC to apply it
   

...