commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jakarta-commons Wiki] Update of "MovingFromSandboxToProperSVN" by MarioIvankovits
Date Tue, 24 May 2005 19:46:03 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.

The following page has been changed by MarioIvankovits:
http://wiki.apache.org/jakarta-commons/MovingFromSandboxToProperSVN

New page:
---
This is a work in progress
---

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 both jakarta-commons
and jakarta-commons-sandbox.  If you don't have karma, ask for it or get someone to help you.

 1. Start vote on commons-dev mailing list, stating reason for promotion of the component.

 1. After vote passes, send announcement with time of move and remind everyone to have any
files in the component checked in by that time.

 1. Actual SVN move:

  i. move project out of sandbox
{{{
$svn move https://svn.apache.org/repos/asf/jakarta/commons/sandbox/vfs https://svn.apache.org/repos/asf/jakarta/commons/proper/vfs
}}}

  i. tag the current sandbox version
{{{
$svn copy https://svn.apache.org/repos/asf/jakarta/commons/proper/vfs/trunk https://svn.apache.org/repos/asf/jakarta/commons/proper/vfs/tags/sandbox
}}}

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.

 1. Make sure your component still builds OK by building it in its new home.

 1. Update the web site for your component.  Start with maven clean if your site is mavenized.
 Your site should now be at jakarta.apache.org/commons/foo rather than jakarta.apache.org/commons/sandbox/foo
 The easiest way to update a mavenized site once you've built and tested it locally is to
run 
{{{
$maven -Dmaven.username=${apache.username} site:sshdeploy
}}}

 1. 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).

 1. Send an announcement to commons-dev and commons-user announcing the move.

 1. Gather a list of committers for the component, ask pmc@jakarta.apache.org to give them
commit access to component in commons-proper.

 1. Start planning a release ;)

(Appendix)

 1. Check-out jakarta-site2 and edit jakarta-site2/xdocs/index.xml and news.xml. Put a news
of "Commons-XX graduated from Sandbox to Commons-Proper"

 

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message