commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Commons Wiki] Update of "MovingFromSandboxToProperSVN" by DennisLundberg
Date Sun, 05 Aug 2007 20:39:07 GMT
Dear Wiki user,

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

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

The comment on the change is:
TLP changes

------------------------------------------------------------------------------
- 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.
+ 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 commons (not just commons-sandbox).
If you don't have karma, get someone to help you.
  
-  1. Start a proposal thread on the commons-dev mailing list, stating reasons for promotion
of the component.
+  1. Start a proposal thread on the dev mailing list, stating reasons for promotion of the
component.
  
-  1. After addressing any concerns about the proposal, start a vote on commons-dev mailing
list.
+  1. After addressing any concerns about the proposal, start a vote on dev mailing list.
  
   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.
  
@@ -13, +13 @@

   1. Tag the current version
  
  {{{
- $svn move https://svn.apache.org/repos/asf/jakarta/commons/sandbox/{prj} https://svn.apache.org/repos/asf/jakarta/commons/proper/{prj}
+ $svn move https://svn.apache.org/repos/asf/commons/sandbox/{prj} https://svn.apache.org/repos/asf/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
+ $svn copy https://svn.apache.org/repos/asf/commons/proper/{prj}/trunk https://svn.apache.org/repos/asf/commons/proper/{prj}/tags/sandbox
  }}}
  
   1. Remove from trunk-sandbox
  {{{
- $svn -N checkout https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox trunk-sandbox
+ $svn -N checkout https://svn.apache.org/repos/asf/commons/trunks-sandbox trunk-sandbox
  $svn propedit svn:externals trunk-sandbox
  $svn commit trunk-sandbox
  }}}
@@ -29, +29 @@

  
   1. Add to trunk-proper
  {{{
- $svn -N checkout https://svn.apache.org/repos/asf/jakarta/commons/trunks-proper trunks-proper
+ $svn -N checkout https://svn.apache.org/repos/asf/commons/trunks-proper trunks-proper
  $svn propedit svn:externals trunks-proper
  $svn commit trunks-proper
  }}}
  When "propedit": go to the end of the list and add your project
  
- 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.
+ That's it for the actual SVN move.  Verify the move succeeded by doing a clean checkout
of 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 
+  1. Update the web site for your component.  Start with maven clean if your site is mavenized.
 Your site should now be at commons.apache.org/foo rather than commons.apache.org/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
  }}}
  
  Maybe you have to checkout commons-build now. You can do this by using
  {{{
- $svn co https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk commons-build
+ $svn co https://svn.apache.org/repos/asf/commons/proper/commons-build/trunk commons-build
  }}}
  on the same level as your project-directory.
  
   1. If you have update your gump.xml and project.xml
  
-  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. Update the commons web site to reflect your component's move.  You will need to update
the menus under commons/commons-build/menus (components-items.ent and sandbox-items.ent),
as well as the more descriptive listings under 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. Send an announcement to dev and user mailing lists 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. Gather a list of committers for the component, ask pmc@commons.apache.org to give them
commit access to component in commons-proper.
  
   1. Start planning a release ;)
  

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


Mime
View raw message