[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[leafnode-list] Re: status of leafnode 2 and how to upgrade from leafnode 1
Joerg Dietrich <joerg@xxxxxxxxxxxx> writes:
>> It is alpha because I don't care too much for compatibility between
>> leafnode-2 versions until I'm happy with it (not much work has been done
>> to leafnode-2 in the past weeks since I've been busy with difficult
>> fetchmail bug fixes). Else, I know of few bugs that hinder daily
>> personal use and am usually quick to fix bugs given the report is
>> substantiated (for instance, with a stack backtrace).
> As someone who contributed a substantial amount of code in the
> past, I find this a very frustrating status.
Thanks for your contributions and concerns.
> Since 2000 leafnode-2 provides significant improved features over
> leafnode-1. I have been using leafnode-2 in production mode for four
> or five years now. I really do not understand what keeps you from
> releasing it instead of keeping it in alpha stage for 5 years and
> still supporting leafnode-1, which has been technically obsoleted by
> many improvements in leafnode-2.
My concern mostly is that switching to leafnode-2 without reviewing
leafnode-1 changes if they need to be ported will cause regressions, and
that leafnode-1 is much better debugged than leafnode-2.
Of course I can rename TODO into TODO.3.0 and release what we have now,
but I fear I'll constantly be unhappy with its state, not being able to
move to 3.0 quickly, with 2.0 bugfixes tying up resources.
leafnode-list mailing list