mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bf_...@brainlounge.de>
Subject Re: svn commit: r771618 - /mina/sandbox/vysper/branches/MINA2.0/
Date Mon, 18 May 2009 08:12:11 GMT
Emmanuel Lecharny wrote:
> Bernd Fondermann wrote:
>> Ashish wrote:
>>  
>>>> All or most files have been changed.
>>>>
>>>> I'd recommend to re-create the branch to reduce merge efforts later.
>>>>       
>>> Feel free to create one. I am yet to start work on it.
>>> Tied with my work right now.
>>>     
>>
>> So, should I remove the branch and we'll create it again when somebody
>> is actually going to work on it, how does that sound? I see no point in
>> an aging branch nobody is committing to.
>>   
> Having done such a move (for Directory, 1.1.7 -> 2.0.0), my experience
> is that it should be done in one shot, when you have time to do it. In
> my case, it took 2 months because I was quite busy and there were deadly
> bugs in MINA I had to fix. But as MINA has stabilized since then, my
> estimation of a move to MINA 2.0 is that it should take a couple of
> days, may be less if you know how MINA work. Probably less than a few
> hours too.
> 
> So just do it in a branch *when* you are ready to do the migration (you
> = anyone feeling the mood and having the time to do the migration).

The MINA code in Vysper is only a small portion of the code.Doing this
as a side-project should not be as critical as refactoring over the
whole codebase. Steady re-integration of TRUNK into the branch should
help reducing pains, too.

> 
> In the mean time, it's probably better to delete the branch. Dead wood
> is heavy to carry :)

+1. done.

 Bernd

Mime
View raw message