Hi Valeri,

it is a consequence of how we mark fixes on GitHub. The big majority of
issues on 2.1 GA was marked on releases 2.1 RC1-4, so they do not appear on
2.1 GA anymore.
Don't worry, the 2.1 GA is not so far ;-)
Anyway I agree with you, we should find a more consistent way to mark
milestone progress.

Thanks

Luigi


2015-06-22 9:51 GMT+02:00 <[email protected]>:

> Hi guys!
>
> Today is 22 of June, 2.1 GA is coming according to roadmap. Or not, it has
> only 8% completed?
>
> I think it would be nice to refresh milestones, and keep roadmap more...
> realistic. Guess you dont expect 2.1 release in a short time, 2.0.12 is not
> planned at all. 2.1-rc4 and 2.0.11 still have blockers. 2.1 is in active
> development since winter, 8% means it is coming next year, and no any
> releases before?
>
> For me OrientDB looks promising, main problem is stability. And of course,
> it is hard to plan something when you cant understand the roadmap
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to