@phalcon, hello. Could you please answer to my questions:
Current branch 2.0.0 is unstable: https://travis-ci.org/phalcon/cphalcon/jobs/44463955 . Tests are failing. Why you merge failing pull requests? Why you don't want to show real build status: https://github.com/phalcon/cphalcon/pull/2999 ?
All sqlite tests are failing, some research about it: https://github.com/phalcon/cphalcon/issues/3123 . Comment please.
I have several pull requests without any comments: https://github.com/phalcon/cphalcon/pulls/quantum13 . Could you please review it.
What result progress of 2.0? This doc is outdated: https://github.com/phalcon/cphalcon/wiki/Progress-2.0
What is the planning release date of 2.0?
- What tasks can I do to help release 2.0?
Also I still want to do feature described below. Please comment it (can be merged in 2.0, 2.x or will not merged):
- Related to one of the oldest open issues https://github.com/phalcon/cphalcon/issues/440 . I want to make not nul validations real NOT NULL, not empty. Logic like https://forum.phalcon.io/discussion/4208/a-proplem-all-fields-need-to-set-upcreate-or-save#C14013 but with checking of default values (I need https://github.com/phalcon/cphalcon/pull/3113 for it). I think it critical feature to ORM.