river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: Release 3.0 merge into trunk
Date Tue, 22 Sep 2015 13:40:01 GMT
For moving to Git, see http://www.apache.org/dev/writable-git

Is the support provided sufficient? How do committers in general feel 
about moving River to Git? If it is a good idea, should we do it before 
Release 3.0? The alternative might be to rename the current SVN branch 
and release from there.

On 9/22/2015 4:31 AM, Bryan Thompson wrote:
> SVN gets really messy for this sort of thing.  We wound not bringing a
> project with a large delta back to the trunk because of these issues and
> just did releases from branches after that.
>
> What kind of support does Apache offer for switching to git?  That might be
> easier.
>
> Thanks,
> Bryan
>
> On Mon, Sep 21, 2015 at 4:49 PM, Patricia Shanahan <pats@acm.org> wrote:
>
>> I think the next thing we need to do to make Release 3.0 a reality is to
>> merge it into the trunk.
>>
>> If you agree, I would like opinions on the best way to go about it.
>> Ideally, we will preserve revision history for modules that have moved from
>> one directory/package to another.
>>
>

Mime
View raw message