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 jakarta- commons (not just jakarta- commons-sandbox). If you don't have karma, get someone to help you.
- Start a proposal thread on the commons- dev mailing list, stating reasons for promotion of the component.
- After addressing any concerns about the proposal, start a vote on commons- dev mailing list.
- After vote passes, send announcement with time of move and remind everyone to have any files in the component checked in by that time.
- Move project in SVN
- Tag the current version
| No Format |
|---|
$svn move https://svn.apache.org/repos/asf/jakarta/commons/sandbox/{prj} https://svn.apache.org/repos/asf/jakarta/commons/proper/{prj} $svn copy https://svn.apache.org/repos/asf/jakarta/commons/proper/{prj}/trunk https://svn.apache.org/repos/asf/jakarta/commons/proper/{prj}/tags/sandbox |
...
| No Format |
|---|
$svn -N checkout https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox trunk-sandbox
$svn propedit svn:externals trunk-sandbox
$svn commit trunk-sandbox
|
...
| No Format |
|---|
$svn -N checkout https://svn.apache.org/repos/asf/jakarta/commons/trunks-proper trunks-proper
$svn propedit svn:externals trunks-proper
$svn commit trunks-proper
|
...
That's it for the actual SVN move. Verify the move succeeded by doing a clean checkout of jakarta- commons. Verify the SVN Repository has picked up the changes correctly. You could to this by enter the svn url in your browser.
- Make sure your component still builds OK by building it in its new home.
- Update the web site for your component. Start with maven clean if your site is mavenized. Your site should now be at jakartacommons.apache.org/commons/foo rather than jakartacommons.apache.org/commons/sandbox/foo The easiest way to update a mavenized site once you've built and tested it locally is to run
...
| No Format |
|---|
$svn co https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk commons-build
|
...
- 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 jakarta- commons/commons-build/menus (components-items.ent and sandbox-items.ent), as well as the more descriptive listings under jakarta- commons/commons-build/parts (components-table.ent and sandbox-table.ent).
- Send an announcement to commons- dev and commons- user mailing lists announcing the move.
- Gather a list of committers for the component, ask pmc@jakartapmc@commons.apache.org to give them commit access to component in commons-proper.
- Start planning a release
...