Release Schedules and Feedback on Fixes

[Ruslan Zasukhin]

On 12/06/15 7:20 PM, "Joakim Schramm" <joakim at astrocalc.com> wrote:

> This is the point the others have tried to get through to you with, we need
> stable releases that last AND by branching this doesn't have to delay
> further development or the speed of it. It's just that it is just that,
> development NOT production - yet.
> 
> My advice is that you branch NOW, this is a good time. Let 2.5 mature, in
> 15-20 days you can release 2.6 BETA but I don't think you need to hurry with
> that - hey it's soon christmas holidays, you need so rest and good food to.
> Taking a step out sometimes give a better perspective and inspires to new
> ideas. And actually, I belive almost none of Valentinas current users would
> really like to see a new version that soon. It is better if you maintain
> what you just have released and... Well I think I have said most above. I
> think it's better if next release would be 2.5.1 and then 2.5.2 maybe, if
> needed. And maybe put 2.6 on hold and move forward to 3.0 in your main
> development, while you maintain 2.5 - it would also give you more freedom,
> less preasure and free speed! Can it bee better? Instead of 2.6, use the
> time to study branching and a source control tool, like CVS, Subversion or
> what ever you like to use.
> 
> Ok that's it from me about this.

I see. 

In other words you say:

    do not make for us 2.6 version with SQL VIEWS and
    UTF-8 support in nearest time?

:-)


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]