Re: Move to git (Was: Re: httpd 2.4 -> next)

Jim Jagielski <[email protected]>
Newsgroups gmane.comp.apache.devel
Message-ID <[email protected]>

> On Feb 10, 2025, at 10:22 AM, Ruediger Pluem <[email protected]> wrote:
> 
> 
> 
> On 1/29/25 12:48 PM, Jim Jagielski wrote:
>> 
>> 
>>> On Jan 28, 2025, at 2:21 PM, Ruediger Pluem <[email protected]> wrote:
>>> 
>>> 
>>> 
>>> On 1/27/25 1:35 PM, Jim Jagielski wrote:
>>>> Now that we have a release out, which gives us, hopefully, some breathing room, should we migrate over to git in earnest? Or
>>>> maybe, at least, document a series of tasks required to do so that we _can_ migrate?
>>> 
>>> Eric already started a confluence page for this:
>>> 
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311628229
>>> 
>> 
>> Thanks! So far the page sez:
>> 
>> 
>>    Items needed day zero
>> 
>> 1. ???
> 
> I added some comments on the page. Some of the points below on the page are IMHO needed by day zero. The release scripts could be
> developed while we are still on svn in a branch. Hence we would still be able to do a fast release once we switched to git which
> seems important in case of a need for an emergency release.
> 

I posted this on the wiki. An alternative might be to move all the support repos "officially" to git, which would allow them to be worked on...

I am just unsure how much we can do to handle the move to git without the source code actually, canonically, being on git (if you get my meaning :) )

--
Jim

 "Grasping the vine with one hand, he plucked the strawberry with the other.
  How sweet it tasted!"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.