You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2005/08/31 22:04:04 UTC

[jira] Created: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Migrate Tomcat to Subversion (Phase 3)
--------------------------------------

         Key: INFRA-536
         URL: http://issues.apache.org/jira/browse/INFRA-536
     Project: Infrastructure
        Type: Improvement
  Components: Subversion  
 Reporter: Mark Thomas
    Priority: Minor


It is now the turn of the servletapi repositories.

We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
- migrate to test repo
- I'll write & test a script to do the moves
- do live migration and apply script

The servletapi dir has particular security requirements. These are:
- It must not be read/write to the Tomcat PMC
- It should be read/write to the follow committers

craigmcc,dannyc,eduardop,jfarcand,jhunter,jon,kinman,patrickl,remm

The repositories to migrate (standard trunk/branches/tags migration) are:

jakarta-servletapi   -> \tomcat\servletapi\servletapi
jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5

Notification mails should go to tomcat-dev

Cheers,

Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/INFRA-536?page=comments#action_12320859 ] 

Henri Yandell commented on INFRA-536:
-------------------------------------

Migrated at 11pm (5 hours ago) last night, then fell asleep while dealing with a crying baby so didn't get to check on the result. Didn't look good though, ended up with a servletapi/servletapi-5/trunk/jakarta-servletapi5 directory. Same for 4. 

Repeated, but as I was fuzzy headed I didn't notice I was looking at viewcvs (which showed the previous attempt even after refreshing due to the nature of svn) :) So repeated to test, repeated to live and looks good now.

http://svn.apache.org/repos/asf/tomcat/servletapi/

svn co https://svn.apache.org/repos/asf/tomcat/servletapi/servletapi/trunk jakarta-servletapi
svn co https://svn.apache.org/repos/asf/tomcat/servletapi/servletapi-4/trunk jakarta-servletapi-4
svn co https://svn.apache.org/repos/asf/tomcat/servletapi/servletapi-5/trunk jakarta-servletapi-5

Close the issue if it all looks good :) 


> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Assignee: Henri Yandell
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/INFRA-536?page=all ]

Henri Yandell reassigned INFRA-536:
-----------------------------------

    Assign To: Henri Yandell

> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Assignee: Henri Yandell
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/INFRA-536?page=all ]
     
Mark Thomas closed INFRA-536:
-----------------------------


All looks fine. Thanks.

> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Assignee: Henri Yandell
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/INFRA-536?page=comments#action_12320748 ] 

Henri Yandell commented on INFRA-536:
-------------------------------------

Test repository migration complete:

http://svn.apache.org/repos/test/tomcat/servletapi/

svn co https://svn.apache.org/repos/test/tomcat/servletapi/servletapi/trunk tomcat-servletapi
svn co https://svn.apache.org/repos/test/tomcat/servletapi/servletapi-4/trunk tomcat-servletapi-4
svn co https://svn.apache.org/repos/test/tomcat/servletapi/servletapi-5/trunk tomcat-servletapi-5

Have at it :)

> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Assignee: Henri Yandell
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/INFRA-536?page=all ]
     
Henri Yandell resolved INFRA-536:
---------------------------------

    Resolution: Fixed

Last one not meant to be a comment. Close if looks good.

> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Assignee: Henri Yandell
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/INFRA-536?page=all ]

Mark Thomas updated INFRA-536:
------------------------------

    Description: 
It is now the turn of the servletapi repositories.

We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
- migrate to test repo
- I'll write & test a script to do the moves
- do live migration and apply script

The repositories to migrate (standard trunk/branches/tags migration) are:

jakarta-servletapi   -> \tomcat\servletapi\servletapi
jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5

Standard tomcat-pmc read/write permissions are fine.

Notification mails should go to tomcat-dev.

Cheers,

Mark

  was:
It is now the turn of the servletapi repositories.

We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
- migrate to test repo
- I'll write & test a script to do the moves
- do live migration and apply script

The servletapi dir has particular security requirements. These are:
- It must not be read/write to the Tomcat PMC
- It should be read/write to the follow committers

craigmcc,dannyc,eduardop,jfarcand,jhunter,jon,kinman,patrickl,remm

The repositories to migrate (standard trunk/branches/tags migration) are:

jakarta-servletapi   -> \tomcat\servletapi\servletapi
jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5

Notification mails should go to tomcat-dev

Cheers,

Mark


Editing issue to remove special security requirements after discussion with Remy (PMC chair)

> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (INFRA-536) Migrate Tomcat to Subversion (Phase 3)

Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/INFRA-536?page=comments#action_12320826 ] 

Mark Thomas commented on INFRA-536:
-----------------------------------

The test repos look good to me. Please migrate as is. Given our change of mind re access controls, I can move them around once the migration has taken place.

> Migrate Tomcat to Subversion (Phase 3)
> --------------------------------------
>
>          Key: INFRA-536
>          URL: http://issues.apache.org/jira/browse/INFRA-536
>      Project: Infrastructure
>         Type: Improvement
>   Components: Subversion
>     Reporter: Mark Thomas
>     Assignee: Henri Yandell
>     Priority: Minor

>
> It is now the turn of the servletapi repositories.
> We have quite a bit of moving around to do here so the way I would like to tackle this is as follows:
> - migrate to test repo
> - I'll write & test a script to do the moves
> - do live migration and apply script
> The repositories to migrate (standard trunk/branches/tags migration) are:
> jakarta-servletapi   -> \tomcat\servletapi\servletapi
> jakarta-servletapi-4 -> \tomcat\servletapi\servletapi-4
> jakarta-servletapi-5 -> \tomcat\servletapi\servletapi-5
> Standard tomcat-pmc read/write permissions are fine.
> Notification mails should go to tomcat-dev.
> Cheers,
> Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira