Re: [Git migration] Old git repositories
On Mon, May 21, 2018 at 3:57 PM, Mark Thomas wrote: > On 04/05/18 10:22, Konstantin Kolinko wrote: > > 2018-04-30 23:48 GMT+03:00 Mark Thomas : > >> The current plan is to merge all of the existing branches into a single > >> Git repo. This will be mirrored at GitHub under apache/tomcat. This is > >> currently used for the svn mirror for trunk only. > >> > >> This raises the question what to do with: > >> apache/tomcat7 > >> apache/tomcat8 > >> apache/tomcat85 > >> > >> I think there are two options: > >> > >> 1. Retain them but make them read-only > >> > >> 2. Delete them > >> > >> Suggestions for other options welcome. > >> > >> I'm actually leaning towards deleting them. [...] > > > > Option 3. Keep repository, but replace it with some README.md > > with an instruction on where to look for the code. > > > > > > A problem that I just stumbled upon: > > See comment #17 in > > https://bz.apache.org/bugzilla/show_bug.cgi?id=43925 > > > > That comment moved discussion from Bugzilla into PR in tomcat70. > > If tomcat70 git repository is deleted, that PR and discussion in it > > will be lost. > > The discussion should have been copied to the dev@ list. Maybe that > isn't setup properly. > > There are only a very small number if issues like this. We can always > manually copy content to the mailing list and/or Bugzilla to keep a copy. > > Given the general preference for deleting them, my proposal is a > combination of all of the above which is. > > Make them read only. Review to ensure we have everything. Copy across > anything we haven't got on list or in Bugzilla to the list/Bugzilla as > appropriate. Then delete them. > > Thoughts? > +1, sounds good to me. > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: [Git migration] Old git repositories
On 04/05/18 10:22, Konstantin Kolinko wrote: > 2018-04-30 23:48 GMT+03:00 Mark Thomas : >> The current plan is to merge all of the existing branches into a single >> Git repo. This will be mirrored at GitHub under apache/tomcat. This is >> currently used for the svn mirror for trunk only. >> >> This raises the question what to do with: >> apache/tomcat7 >> apache/tomcat8 >> apache/tomcat85 >> >> I think there are two options: >> >> 1. Retain them but make them read-only >> >> 2. Delete them >> >> Suggestions for other options welcome. >> >> I'm actually leaning towards deleting them. [...] > > Option 3. Keep repository, but replace it with some README.md > with an instruction on where to look for the code. > > > A problem that I just stumbled upon: > See comment #17 in > https://bz.apache.org/bugzilla/show_bug.cgi?id=43925 > > That comment moved discussion from Bugzilla into PR in tomcat70. > If tomcat70 git repository is deleted, that PR and discussion in it > will be lost. The discussion should have been copied to the dev@ list. Maybe that isn't setup properly. There are only a very small number if issues like this. We can always manually copy content to the mailing list and/or Bugzilla to keep a copy. Given the general preference for deleting them, my proposal is a combination of all of the above which is. Make them read only. Review to ensure we have everything. Copy across anything we haven't got on list or in Bugzilla to the list/Bugzilla as appropriate. Then delete them. Thoughts? Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [Git migration] Old git repositories
2018-04-30 23:48 GMT+03:00 Mark Thomas : > The current plan is to merge all of the existing branches into a single > Git repo. This will be mirrored at GitHub under apache/tomcat. This is > currently used for the svn mirror for trunk only. > > This raises the question what to do with: > apache/tomcat7 > apache/tomcat8 > apache/tomcat85 > > I think there are two options: > > 1. Retain them but make them read-only > > 2. Delete them > > Suggestions for other options welcome. > > I'm actually leaning towards deleting them. [...] Option 3. Keep repository, but replace it with some README.md with an instruction on where to look for the code. A problem that I just stumbled upon: See comment #17 in https://bz.apache.org/bugzilla/show_bug.cgi?id=43925 That comment moved discussion from Bugzilla into PR in tomcat70. If tomcat70 git repository is deleted, that PR and discussion in it will be lost. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [Git migration] Old git repositories
2018-04-30 16:48 GMT-04:00 Mark Thomas : > > The current plan is to merge all of the existing branches into a single > Git repo. This will be mirrored at GitHub under apache/tomcat. This is > currently used for the svn mirror for trunk only. > > This raises the question what to do with: > apache/tomcat7 > apache/tomcat8 > apache/tomcat85 > > I think there are two options: > > 1. Retain them but make them read-only > > 2. Delete them +1 delete them Regards, Violeta > Suggestions for other options welcome. > > I'm actually leaning towards deleting them. My reasoning is that we > deleted apache/tomcat55 and apache/tomcat6 when those releases reached > EOL and no-one complained. As far as I recall, no-one even mentioned the > deletions on list. Therefore, I'd be happy to delete those mirrors just > as soon as apache/tomcat was up and running. > > Mark > > P.S. Don't forget that apache/tomcat will become writeable as part of > the migration and will sync with gitbox.apache.org in a dual master > configuration > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org >
Re: [Git migration] Old git repositories
+1 for deleting them. On Tue, May 1, 2018 at 5:36 AM, Coty Sutherland wrote: > On Mon, Apr 30, 2018, 16:48 Mark Thomas wrote: > >> The current plan is to merge all of the existing branches into a single >> Git repo. This will be mirrored at GitHub under apache/tomcat. This is >> currently used for the svn mirror for trunk only. >> >> This raises the question what to do with: >> apache/tomcat7 >> apache/tomcat8 >> apache/tomcat85 >> >> I think there are two options: >> >> 1. Retain them but make them read-only >> >> 2. Delete them >> >> Suggestions for other options welcome. >> >> I'm actually leaning towards deleting them. My reasoning is that we >> deleted apache/tomcat55 and apache/tomcat6 when those releases reached >> EOL and no-one complained. As far as I recall, no-one even mentioned the >> deletions on list. Therefore, I'd be happy to delete those mirrors just >> as soon as apache/tomcat was up and running. >> > > I don't see a reason for keeping them so I'm +1 for deleting them. > > >> Mark >> >> P.S. Don't forget that apache/tomcat will become writeable as part of >> the migration and will sync with gitbox.apache.org in a dual master >> configuration >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> >> -- Best Regards！ Huxing - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [Git migration] Old git repositories
On Mon, Apr 30, 2018, 16:48 Mark Thomas wrote: > The current plan is to merge all of the existing branches into a single > Git repo. This will be mirrored at GitHub under apache/tomcat. This is > currently used for the svn mirror for trunk only. > > This raises the question what to do with: > apache/tomcat7 > apache/tomcat8 > apache/tomcat85 > > I think there are two options: > > 1. Retain them but make them read-only > > 2. Delete them > > Suggestions for other options welcome. > > I'm actually leaning towards deleting them. My reasoning is that we > deleted apache/tomcat55 and apache/tomcat6 when those releases reached > EOL and no-one complained. As far as I recall, no-one even mentioned the > deletions on list. Therefore, I'd be happy to delete those mirrors just > as soon as apache/tomcat was up and running. > I don't see a reason for keeping them so I'm +1 for deleting them. > Mark > > P.S. Don't forget that apache/tomcat will become writeable as part of > the migration and will sync with gitbox.apache.org in a dual master > configuration > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
[Git migration] Old git repositories
The current plan is to merge all of the existing branches into a single Git repo. This will be mirrored at GitHub under apache/tomcat. This is currently used for the svn mirror for trunk only. This raises the question what to do with: apache/tomcat7 apache/tomcat8 apache/tomcat85 I think there are two options: 1. Retain them but make them read-only 2. Delete them Suggestions for other options welcome. I'm actually leaning towards deleting them. My reasoning is that we deleted apache/tomcat55 and apache/tomcat6 when those releases reached EOL and no-one complained. As far as I recall, no-one even mentioned the deletions on list. Therefore, I'd be happy to delete those mirrors just as soon as apache/tomcat was up and running. Mark P.S. Don't forget that apache/tomcat will become writeable as part of the migration and will sync with gitbox.apache.org in a dual master configuration - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
