www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-5390) Migrate maven to git
Date Sun, 11 Nov 2012 10:05:12 GMT

    [ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494848#comment-13494848
] 

Christofer Dutz edited comment on INFRA-5390 at 11/11/12 10:05 AM:
-------------------------------------------------------------------

As we were having the same discussion in the flex-dev group; I'll simply post the summary
I posted there in this issue too:

Yesterday I have to admit that I was sort of confused after reading the posts on this list
about Subversion, Git and which repos are available and how changes are transfered to what
repos. So at lunch I saw Gavin from the infrastructure team sitting on the table next to me,
so I sort of took the opportunity to clarify stuff for me. I thought this might be interesting
for the rest ... so here goes (Just think of all references to "flex-dev" as being "maven-dev"
... I think you should get the point though):

Currenntly each project under the hood of Apache has two choices:

Choice number one: Subversion (Currently used by Flex)
-------------------------------------------------------------
In this case there is a subversion repo available. This is currently what the flex project
uses.

There is a svn repo available at https://svn.apache.org/repos/asf/{top-level-project-name}<https://svn.apache.org/repos/asf/%7btop-level-project-name%7d>
or https://svn.apache.org/repos/asf/incubator/{incubator-project-name}<https://svn.apache.org/repos/asf/incubator/%7bincubator-project-name%7d>.
For flex this is: https://svn.apache.org/repos/asf/incubator/flex/sdk



Each SVN repo is automatically cloned to Github https://github.com/apache/ flex' repo is available
under https://github.com/apache/flex-sdk

If the Subversion repo is updated, this change is automatically replicated to the github repo
in about 5 minutes. However changes to the Github repo are NOT AUTOMATICALLY sent back to
the subversion repository. This has to be done manually.



Every project can REQUEST to have a read-only git repo hosted at http://git.apache.org/ for
the flex project this is git://git.apache.org/flex-sdk.git on the http://git.apache.org/ page
there are also some links to both the git.apache.org as well as the github clones.




Choice number two: Git
-------------------------------------------------------------
Currently Apache seems to offer it's projects the alternative to use git as a central repository.
This is available under: https://git-wip-us.apache.org/ but the Project has to officially
request this to be changed. In contradiction to the "BIG FREAKING NOTE<https://git-wip-us.apache.org/docs/switching-to-git.html#contents>"
on the page, it seems that project are allready using this. As the "wip = Work in Progress"
suggests, the url will certainly change in the near future.

Syncing this with github should be easyly handled.



The process of swithing seems to be that at a given time the project confirms that the current
state of the git-readonly-clone should be used as base of the new git repo and then simply
that repo is cloned to: https://git-wip-us.apache.org/. The only thing that would stay in
subcersion would be the content of the website, as this currently doesn't support git.



                
      was (Author: cdutz):
    As we were having the same discussion in the flex-dev group; I'll simply post the summary
I posted there in this issue too:

Yesterday I have to admit that I was sort of confused after reading the posts on this list
about Subversion, Git and which repos are available and how changes are transfered to what
repos. So at lunch I saw Gavin from the infrastructure team sitting on the table next to me,
so I sort of took the opportunity to clarify stuff for me. I thought this might be interesting
for the rest ... so here goes:

Currenntly each project under the hood of Apache has two choices:

Choice number one: Subversion (Currently used by Flex)
-------------------------------------------------------------
In this case there is a subversion repo available. This is currently what the flex project
uses.

There is a svn repo available at https://svn.apache.org/repos/asf/{top-level-project-name}<https://svn.apache.org/repos/asf/%7btop-level-project-name%7d>
or https://svn.apache.org/repos/asf/incubator/{incubator-project-name}<https://svn.apache.org/repos/asf/incubator/%7bincubator-project-name%7d>.
For flex this is: https://svn.apache.org/repos/asf/incubator/flex/sdk



Each SVN repo is automatically cloned to Github https://github.com/apache/ flex' repo is available
under https://github.com/apache/flex-sdk

If the Subversion repo is updated, this change is automatically replicated to the github repo
in about 5 minutes. However changes to the Github repo are NOT AUTOMATICALLY sent back to
the subversion repository. This has to be done manually.



Every project can REQUEST to have a read-only git repo hosted at http://git.apache.org/ for
the flex project this is git://git.apache.org/flex-sdk.git on the http://git.apache.org/ page
there are also some links to both the git.apache.org as well as the github clones.




Choice number two: Git
-------------------------------------------------------------
Currently Apache seems to offer it's projects the alternative to use git as a central repository.
This is available under: https://git-wip-us.apache.org/ but the Project has to officially
request this to be changed. In contradiction to the "BIG FREAKING NOTE<https://git-wip-us.apache.org/docs/switching-to-git.html#contents>"
on the page, it seems that project are allready using this. As the "wip = Work in Progress"
suggests, the url will certainly change in the near future.

Syncing this with github should be easyly handled.



The process of swithing seems to be that at a given time the project confirms that the current
state of the git-readonly-clone should be used as base of the new git repo and then simply
that repo is cloned to: https://git-wip-us.apache.org/. The only thing that would stay in
subcersion would be the content of the website, as this currently doesn't support git.



                  
> Migrate maven to git
> --------------------
>
>                 Key: INFRA-5390
>                 URL: https://issues.apache.org/jira/browse/INFRA-5390
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including
renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven,
so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git 
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories
into the new repo, which we will handle in a separate jira later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message