tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: [Git migration] Old git repositories
Date Mon, 21 May 2018 19:57:26 GMT
On 04/05/18 10:22, Konstantin Kolinko wrote:
> 2018-04-30 23:48 GMT+03:00 Mark Thomas <markt@apache.org>:
>> 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message