Next release

Oliver Kraitschy okraits at arcor.de
Sat Jan 30 05:20:58 EST 2016


On Sat, Jan 30, 2016 at 04:29:28AM +0300, Zaid Abdulla wrote:
> 
> I understand your frustration and I'm sorry for the poor communication
> on my part. While I would much prefer to iteratively evolve the
> software, I had no choice but to overhaul much of existing architecture
> in one go for various reasons. The original plan of an intermediate
> release (before architecture change) to include some of the most
> requested features no longer seemed feasible. Not to mention my
> original estimate was overly optimistic. Another reason for the delay
> is that I have to prioritize work for commercial clients and that is
> taking a lot of my time. And no, this isn't just a project I do in my
> spare time :) I've been on this full time for quite a while now.
> 
> Having said that, the next release will maintain backward compatibility
> of API and DB structure for the most part. So you can use the current
> version and upgrade later with ease. I can't give a firm date just yet,
> but I hope towards the end of February we'll have something alpha
> quality. Then I can better estimate how long until it's production
> ready (should be a matter of weeks, not months). Keep an eye on the
> Announce mailing list for an update Soon (TM).

So am I correct that the code on github isn't quite up to date? If that's
correct, when do you push the updates to github? It would be beneficial to
have the latest revision of the code when working on it.

Thank you very much in advance.

Greetings,
Oliver


More information about the Users mailing list