Page History

...

As far as the Commons repository is concerned, a Commons component can be in one and only one of the following states:

• Wiki Markupproper (\[http://svn.apache.org/repos/asf/commons/proper/ current list\]) Wiki Markup
• sandbox (\[http://svn.apache.org/repos/asf/commons/sandbox/ current list\])unmigrated-wiki-markup
• dormant (\[http://svn.apache.org/repos/asf/commons/dormant/ current list\]) \\
  

Pre-requisites

• Any transition where the origin or destination is Commons Proper, requires a VOTE.
• Wiki MarkupRevival from dormancy requires a VOTE (as documented in the "Revival" section of the \[http://commons.apache.org/dormant/index.html dormant components web page\]).
• Wiki MarkupThus effectively the only move that can occur by lazy consensus is the periodic \[http://wiki.apache.org/commons/ProposalSandboxPruning sandbox pruning\] for dormant components. \\
  

So, make sure you have called a VOTE and it has passed.

You will need commons karma.

Sandbox graduations

Wiki MarkupTransitions from sandbox to proper are particularly significant, and have a number of additional tasks associated with them. The appropriate wiki page to consult for sandbox graduations is \[:MovingFromSandboxToProperSVN\].

SVN move

For a component that changes state from <origin> to <destination>:

1. Remove component from svn:externals from the trunks-<origin>
2. Move component
3. Add component to svn:externals in the trunks-<destination>
   

...

The above sequence makes sure that component is always available when listed in the particular svn:externals. The actual SVN commands can be looked up either from the \[:MovingFromSandboxToProperSVN\] or [ProposalSandboxPruning] wiki pages.

Tagging

Tag the component once it has been moved to its new location in SVN. The recommended tag name is:

...