You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@logging.apache.org by Mark Womack <mw...@apache.org> on 2005/10/04 06:33:11 UTC
Re: CVS -> SVN Migration Status
Henri, et al,
I believe we are good to go for the migration, with the following changes:
logging-sandbox : Move the existing cvs dirs into a "log4j" subdir.
logging-site : We need the branches and tags moved over from the cvs repo.
Also, please double check the settings on this repo as I could only checkout
using http, not https. No one else seemed to have this issue, just me.
You had also previously mentioned something about a "core" repo yet to be
converted. I don't know what that one is.
Let us know what the next steps will be. With the above, we are ready to go
(finally).
much appreciated,
-Mark
----- Original Message -----
From: "Mark Womack" <mw...@apache.org>
To: "Logging General" <ge...@logging.apache.org>; <ba...@apache.org>
Sent: Wednesday, September 21, 2005 8:31 PM
Subject: CVS -> SVN Migration Status
> chainsaw - Build process verified (Scott)
>
> log4jcxx - Repository reviewed, still need to verify the build process
> (Curt todo).
>
> log4j - Build process for the head and the 1_2branch verified for the
> classes/jars. Still need to verify the dist builds which are dependent on
> the logging-site repository (see below). (Mark)
>
> log4net - Build process verified (Nicko)
>
> sandbox - Build process verified. But when we move it for real we want to
> move the current code into a sandbox/log4j subdir if we can. If not, then
> we'll just do it manually after the migration. The sandbox will be shared
> by all of the subprojects. (Mark)
>
> site - I still cannot check out the site. Is anyone else encountering
> this, or is it just me? My cygwin svn command line client works fine with
> all of the other repositories except for logging-site. I'll try a
> different client tomorrow evening.
>
> Thanks everyone. With hurricane Rita bearing down on Curt's location we
> may be delayed in completing the entire migration. But we are almost
> there and things are looking good (except for Rita, of course).
>
> -Mark
>
>
Re: CVS -> SVN Migration Status
Posted by Mark Womack <mw...@apache.org>.
Thanks, Henri. I will take a look at the new versions tomorrow.
All, please take a look at your respective subproject related repos. If
there are any issues, now is the time to bring it up. Otherwise we will do
the conversion as Henri mentions.
thanks,
-Mark
----- Original Message -----
From: "Henri Yandell" <ba...@apache.org>
To: "Mark Womack" <mw...@apache.org>
Cc: "Logging General" <ge...@logging.apache.org>
Sent: Tuesday, October 04, 2005 1:16 PM
Subject: Re: CVS -> SVN Migration Status
>
> http://svn.apache.org/repos/test/logging/
>
> I repeated the migration, log4j-sandbox now found in
> logging/sandbox/log4j, and the site now keeps its branches/tags.
>
> See how it looks, unless I hear otherwise I'll go ahead and do the real
> migration at 8pm on Saturday US/Eastern.
>
> Hen
>
> On Mon, 3 Oct 2005, Mark Womack wrote:
>
>> Henri, et al,
>>
>> I believe we are good to go for the migration, with the following
>> changes:
>>
>> logging-sandbox : Move the existing cvs dirs into a "log4j" subdir.
>>
>> logging-site : We need the branches and tags moved over from the cvs
>> repo. Also, please double check the settings on this repo as I could only
>> checkout using http, not https. No one else seemed to have this issue,
>> just me.
>>
>> You had also previously mentioned something about a "core" repo yet to be
>> converted. I don't know what that one is.
>>
>> Let us know what the next steps will be. With the above, we are ready to
>> go (finally).
>>
>> much appreciated,
>> -Mark
>>
>> ----- Original Message ----- From: "Mark Womack" <mw...@apache.org>
>> To: "Logging General" <ge...@logging.apache.org>; <ba...@apache.org>
>> Sent: Wednesday, September 21, 2005 8:31 PM
>> Subject: CVS -> SVN Migration Status
>>
>>
>>> chainsaw - Build process verified (Scott)
>>>
>>> log4jcxx - Repository reviewed, still need to verify the build process
>>> (Curt todo).
>>>
>>> log4j - Build process for the head and the 1_2branch verified for the
>>> classes/jars. Still need to verify the dist builds which are dependent
>>> on the logging-site repository (see below). (Mark)
>>>
>>> log4net - Build process verified (Nicko)
>>>
>>> sandbox - Build process verified. But when we move it for real we want
>>> to move the current code into a sandbox/log4j subdir if we can. If not,
>>> then we'll just do it manually after the migration. The sandbox will be
>>> shared by all of the subprojects. (Mark)
>>>
>>> site - I still cannot check out the site. Is anyone else encountering
>>> this, or is it just me? My cygwin svn command line client works fine
>>> with all of the other repositories except for logging-site. I'll try a
>>> different client tomorrow evening.
>>>
>>> Thanks everyone. With hurricane Rita bearing down on Curt's location we
>>> may be delayed in completing the entire migration. But we are almost
>>> there and things are looking good (except for Rita, of course).
>>>
>>> -Mark
>>>
>>>
>>
>>
>
Re: CVS -> SVN Migration Status
Posted by Mark Womack <mw...@apache.org>.
Ceki (or anyone), can you shed any light on the logging "core" cvs module?
Have we used it for anything?
-Mark
----- Original Message -----
From: <ba...@apache.org>
To: "Mark Womack" <mw...@apache.org>
Cc: "Logging General" <ge...@logging.apache.org>
Sent: Monday, October 03, 2005 9:55 PM
Subject: Re: CVS -> SVN Migration Status
>
> I'll do some work tomorrow on a repeat migration to test to cover the
> sandbox and site issues, then leaving that there for you to check, I'll
> aim to do the real migration on Saturday at 8pm US/Eastern.
>
> -
>
> I'll deal with the various tlp-core modules that are out there at a later
> stage. I think they're private pmc modules, but the fact that you don't
> use yours (by the sound of it) implies they might not be very essential.
>
> I've asked the various root@ people if I could have temporary group
> membership to various tlp's so I can see inside the directories in order
> to get the migration done.
>
> Hen