This wiki page is meant to document the action items when a component changes state.
As far as the Commons repository is concerned, a Commons component can be in one and only one of the following states:
proper (\[http://svn.apache.org/repos/asf/commons/proper/ current list\]) |
sandbox (\[http://svn.apache.org/repos/asf/commons/sandbox/ current list\]) |
dormant (\[http://svn.apache.org/repos/asf/commons/dormant/ current list\]) \\ |
Revival from dormancy requires a VOTE (as documented in the "Revival" section of the \[http://commons.apache.org/dormant/index.html dormant components web page\]). |
Thus 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.
Transitions 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\]. |
For a component that changes state from <origin> to <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. |
Tag the component once it has been moved to its new location in SVN. The recommended tag name is:
<component>_<origin>_mm_yyyy
Example: A component foo that has been moved out of sandbox in January 2006 chooses a tag FOO_SANDBOX_01_2006 after the move.
Update the POM to reflect the correct website URL for the new component state.
The sequence is important to avoid potential 404s.