Re: Migrating to git

2018-01-24 Thread Coty Sutherland
On Wed, Jan 24, 2018 at 4:57 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Coty, > > On 1/24/18 1:34 PM, Coty Sutherland wrote: >> I think this is the right thread to add this :) >> >> Given that we will be able to accept PRs on Github after this >> migrati

Re: Migrating to git

2018-01-24 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Coty, On 1/24/18 1:34 PM, Coty Sutherland wrote: > I think this is the right thread to add this :) > > Given that we will be able to accept PRs on Github after this > migration, do we want to add a Travis (or other CI) configuration > to our repos

Re: Migrating to git

2018-01-24 Thread Mark Thomas
On 24/01/18 18:34, Coty Sutherland wrote: > I think this is the right thread to add this :) > > Given that we will be able to accept PRs on Github after this > migration, do we want to add a Travis (or other CI) configuration to > our repository so that it will do a test build (and maybe test one

Re: Migrating to git

2018-01-24 Thread Coty Sutherland
I think this is the right thread to add this :) Given that we will be able to accept PRs on Github after this migration, do we want to add a Travis (or other CI) configuration to our repository so that it will do a test build (and maybe test one connector) when someone proposes a pull? Doing that

Re: Migrating to git

2017-12-13 Thread Rémy Maucherat
On Wed, Dec 13, 2017 at 10:23 AM, Mark Thomas wrote: > The plan is to switch to "github as master' which is actually a dual > master system where commits can be made directly to either github or the > ASF. I don't think it matter which we use. My (not recent) experience is > that github is faster

Re: Migrating to git

2017-12-13 Thread Mark Thomas
On 12/12/17 13:41, Konstantin Kolinko wrote: >> >> The first draft of this is up. >> >> https://cwiki.apache.org/confluence/display/TOMCAT/Git+migration >> >> Please add any issues either directly to that page or this thread. > > 1. I suspect that existing pull requests / issues at GitHub will be

Re: Migrating to git

2017-12-12 Thread Konstantin Kolinko
> > The first draft of this is up. > > https://cwiki.apache.org/confluence/display/TOMCAT/Git+migration > > Please add any issues either directly to that page or this thread. 1. I suspect that existing pull requests / issues at GitHub will be lost. Maybe they will be kept for tomcat.git repositor

Re: Migrating to git

2017-12-12 Thread Mark Thomas
On 12/12/17 06:48, Rémy Maucherat wrote: > On Mon, Dec 11, 2017 at 10:28 PM, Mark Thomas wrote: > >> On 11/12/17 16:24, Mark Thomas wrote: >>> On 11/12/17 15:27, Rémy Maucherat wrote: >> >> >> Do we get a "demo" repo to see the result ? >>> >>> Because the plan above starts with the existin

Re: Migrating to git

2017-12-11 Thread Rémy Maucherat
On Mon, Dec 11, 2017 at 10:28 PM, Mark Thomas wrote: > On 11/12/17 16:24, Mark Thomas wrote: > > On 11/12/17 15:27, Rémy Maucherat wrote: > > > > >> Do we get a "demo" repo to see the result ? > > > > Because the plan above starts with the existing git mirror when we do > > decide to migrate it

Re: Migrating to git

2017-12-11 Thread Mark Thomas
On 11/12/17 16:24, Mark Thomas wrote: > On 11/12/17 15:27, Rémy Maucherat wrote: >> Do we get a "demo" repo to see the result ? > > Because the plan above starts with the existing git mirror when we do > decide to migrate it will be directly on the live repo. However, I'm > happy to pull togeth

Re: Migrating to git

2017-12-11 Thread Mark Thomas
On 11/12/17 15:27, Rémy Maucherat wrote: > On Wed, Dec 6, 2017 at 2:54 PM, Mark Thomas wrote: > >> On 06/12/17 11:30, Mark Thomas wrote: >>> On 06/12/17 10:34, Konstantin Kolinko wrote: >> >> >> If the goal is to create a single Git repository from our several ones, my suggestion is to

Re: Migrating to git

2017-12-11 Thread Rémy Maucherat
On Wed, Dec 6, 2017 at 2:54 PM, Mark Thomas wrote: > On 06/12/17 11:30, Mark Thomas wrote: > > On 06/12/17 10:34, Konstantin Kolinko wrote: > > > > >> If the goal is to create a single Git repository from our several ones, > >> my suggestion is to create a repository and pull in the branches fro

Re: Migrating to git

2017-12-06 Thread Mark Thomas
On 06/12/17 11:30, Mark Thomas wrote: > On 06/12/17 10:34, Konstantin Kolinko wrote: >> If the goal is to create a single Git repository from our several ones, >> my suggestion is to create a repository and pull in the branches from >> the existing 7/8/8.5/9 git mirrors. > Sounds good. And it

Re: Migrating to git

2017-12-06 Thread Mark Thomas
On 06/12/17 10:34, Konstantin Kolinko wrote: > 2017-12-05 23:03 GMT+03:00 Mark Thomas : >> Hi all, >> >> I've been doing some experiments to see how we might migrate from our >> current svn structure to git. It appears that git svn is able to follow >> directory moves so, with that in mind, I'd lik

Re: Migrating to git

2017-12-06 Thread Konstantin Kolinko
2017-12-05 23:03 GMT+03:00 Mark Thomas : > Hi all, > > I've been doing some experiments to see how we might migrate from our > current svn structure to git. It appears that git svn is able to follow > directory moves so, with that in mind, I'd like to propose the following > outline plan: > > Plan

Re: Migrating to git

2017-12-06 Thread Mark Thomas
On 06/12/17 02:05, Huxing Zhang wrote: > Hi, > > I am +1 on migrating to git. I think this will help people easier to get > involved. > > One quick question to Plan A: > After migration to git, will the previous mirrors, e.g. > https://github.com/apache/tomcat70,

Re: Migrating to git

2017-12-05 Thread Mohamed Abd ALLAH
+1 for git. +1 for Branches instead of tags. On Tue, Dec 5, 2017 at 9:05 PM, Huxing Zhang wrote: > Hi, > > I am +1 on migrating to git. I think this will help people easier to get > involved. > > One quick question to Plan A: > After migration to git, will the previous

Re: Migrating to git

2017-12-05 Thread Huxing Zhang
Hi, I am +1 on migrating to git. I think this will help people easier to get involved. One quick question to Plan A: After migration to git, will the previous mirrors, e.g. https://github.com/apache/tomcat70, be removed? We maintain an internal repository with selective tomcat versions

Re: Migrating to git

2017-12-05 Thread Mark Thomas
On 05/12/17 20:43, Emmanuel Bourg wrote: > Le 05/12/2017 à 21:03, Mark Thomas a écrit : > >> and then migrate /trunk, /tags and /branches to git, leaving the rest in >> place. Most will stay there. Some components may move to git in the future. > > The goal is to put all Tomcat versions in the sa

Re: Migrating to git

2017-12-05 Thread Coty Sutherland
On Tue, Dec 5, 2017 at 3:43 PM, Emmanuel Bourg wrote: > Le 05/12/2017 à 21:03, Mark Thomas a écrit : > >> and then migrate /trunk, /tags and /branches to git, leaving the rest in >> place. Most will stay there. Some components may move to git in the future. > > The goal is to put all Tomcat versio

Re: Migrating to git

2017-12-05 Thread Emmanuel Bourg
Le 05/12/2017 à 21:03, Mark Thomas a écrit : > and then migrate /trunk, /tags and /branches to git, leaving the rest in > place. Most will stay there. Some components may move to git in the future. The goal is to put all Tomcat versions in the same Git repository right? Would that make the svn ta

Migrating to git

2017-12-05 Thread Mark Thomas
Hi all, I've been doing some experiments to see how we might migrate from our current svn structure to git. It appears that git svn is able to follow directory moves so, with that in mind, I'd like to propose the following outline plan: Plan A == 0. Run plan past infra 1. Restructure svn 2.