...
- An inactive component is any component that not had any commits made in the last six months.
- Any component which has been inactive is a candidate for archiving.
- Any inactive component can be archived by lazy consensus.
- A directory called dormant will be created as a child of commons.
- This directory will be read-only except for archiving activities.
- To archive a component, the component directory will be moved from the sandbox to the dormant directory (and removed from trunks-sandbox svn:externals).
- A component can be unarchived (back into the sandbox) by a vote.
- The website for the component will be retained but marked as dormant.
...
Though any component can be archived by lazy consensus, netiquette requires a proposal to give the chance for any committers interested in that component to reply. There is no pressing reason for haste and so an appropriate duration should be chosen for the vote.
Commands
- svn move -m 'moving to dormancy' https://svn.apache.org/repos/asf/jakarta/commons/sandbox/xxxx https://svn.apache.org/repos/asf/jakarta/commons/dormant/xxxx
- svn co -N https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox
- cd trunks-sandbox
- svn propedit svn:externals .
Wiki Markup \[remove xxxx from the externals\]- svn ci -m 'moved xxxx to dormancy'
- svn co -N https://svn.apache.org/repos/asf/jakarta/commons/trunks-dormant
- svn propedit svn:externals .
Wiki Markup \[add xxxx to the externals\]- svn ci -m 'moved xxxx to dormancy'