Moving components to git - what to do with the SVN tree

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Moving components to git - what to do with the SVN tree

Benedikt Ritter-4
Hi,

I've talked to infra and they have set up permission so that PMC members
can write to https://svn.apache.org/repos/asf/commons/_moved_to_git The
process of migrating a component to git is now as follows:

- create infra ticket for migration
- wait for infra to migrate the code
- update SCM location in pom.xml and on the website.
- create a directory in _moved_to_git
- move branches, tags, trunk directories of the component to the directory
in _moved_to_git
- add a FooNowUsesGit.txt file to the old svn location (see
commons/proper/lang for an example)

Regards,
Benedikt
Reply | Threaded
Open this post in threaded view
|

Re: Moving components to git - what to do with the SVN tree

jochen-2
On Sun, Jul 31, 2016 at 1:14 PM, Benedikt Ritter <[hidden email]> wrote:

> I've talked to infra and they have set up permission so that PMC members
> can write to https://svn.apache.org/repos/asf/commons/_moved_to_git The
> process of migrating a component to git is now as follows:

Thanks for the hint. After the permissions have now been adjusted, I
was able to finish moving FileUpload to Git.

Jochen


--
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Moving components to git - what to do with the SVN tree

sebb-2-2
In reply to this post by Benedikt Ritter-4
On 31 July 2016 at 12:14, Benedikt Ritter <[hidden email]> wrote:

> Hi,
>
> I've talked to infra and they have set up permission so that PMC members
> can write to https://svn.apache.org/repos/asf/commons/_moved_to_git The
> process of migrating a component to git is now as follows:
>
> - create infra ticket for migration
> - wait for infra to migrate the code
> - update SCM location in pom.xml and on the website.
> - create a directory in _moved_to_git
> - move branches, tags, trunk directories of the component to the directory
> in _moved_to_git
> - add a FooNowUsesGit.txt file to the old svn location (see
> commons/proper/lang for an example)

Note that this leaves all the _moved_to_git files writable by the PMC.

There are possible solutions to this, but the effort might not be worth it.

> Regards,
> Benedikt

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Moving components to git - what to do with the SVN tree

jochen-2
On Thu, Aug 18, 2016 at 4:27 PM, sebb <[hidden email]> wrote:

> Note that this leaves all the _moved_to_git files writable by the PMC.

I fail to consider that a problem. It is SVN, after all, so the
initial state will always be restorable.

Jochen


--
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Moving components to git - what to do with the SVN tree

Konstantin Kolinko
In reply to this post by Benedikt Ritter-4
2016-07-31 14:14 GMT+03:00 Benedikt Ritter <[hidden email]>:

> Hi,
>
> I've talked to infra and they have set up permission so that PMC members
> can write to https://svn.apache.org/repos/asf/commons/_moved_to_git The
> process of migrating a component to git is now as follows:
>
> - create infra ticket for migration
> - wait for infra to migrate the code
> - update SCM location in pom.xml and on the website.
> - create a directory in _moved_to_git
> - move branches, tags, trunk directories of the component to the directory
> in _moved_to_git
> - add a FooNowUsesGit.txt file to the old svn location (see
> commons/proper/lang for an example)

You are missing "Remove the project from the svn:externals property of
the trunks-proper directory: " step, as documented on the wiki,

https://wiki.apache.org/commons/MovingToGit


>
> Regards,
> Benedikt

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]