[rules-dev] the new drools 5.0 api and the old api

Drools 5.0 comes with a new API. I also suspect that the new api is located in a new package drools-api. Ideally new software written will start using the new API. Ideally it would be nice to separate the old api in a separate package called something like drools-api-legacy, and I am sure that is the goal. Would it make sense to add @deprecated to the old api? It would make thing a little bit clearer for the devs who write code against the api. regards --zoly