THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
No Format |
---|
$maven -Dmaven.username=${apache.username} site:sshdeploy |
Maybe you have to checkout Checkout commons-build now. You - you can do this by using
No Format |
---|
$svn co https://svn.apache.org/repos/asf/commons/proper/commons-build/trunk commons-build |
on the same level as your project-directory.
- If you have update your gump.xml and project.xml
- 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).
- Update
/www/commons.apache.org/sandbox/.htaccess
and add a "Redirect permanent" to have automatic redirection from your projects sandbox to the proper website. - Send an announcement to dev and user mailing lists announcing the move.
- Gather a list of committers for the component, ask pmc@commonsdev@commons.apache.org to give them commit access to component in commons-proper.
- Start planning a release
(Appendix)
- Check-out jakarta-site
- edit jakarta-site/news.xml. Put a news of "Commons-XXXX graduated from Sandbox to Commons-Proper"
- 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.
No Format |
---|
$svn co https://svn.apache.org/repos/asf/jakarta/site
|
- Edit xdocs/site/news.xml
And follow docs/README.txt to regenerate the site. Check if it looks good.
- Create a diff of your changes and ask a PMC to apply it
...