Hi all,

triggered by the API redesign discussion following up on the hydrogen
adder problem, it might be wise to discuss release plans.
Since we do not have no formal release managers at this moment (that's
two vacancies in the project! you can earn some good CDK fame here),
it might be useful to summarize the state of things.

1. trunk/

* JUnit4 transition ongoing
* Java5 cleanup ongoing
* but is stabilizing (*)
* it is much more performant (**)

*) there are problems with IP calculation, reactions, etc, which I
hope to address next week Friday

**) someone reported on IRC SMILES parsing going down from 4 hours
(cdk-1.0.x) to 5 seconds (trunk).
Really. Not suprising for those who are aware of the problems with
using the AllRingsFinder algorithm, which
simply features a combinatorial explosion for detecting all rings...
(E.g. see CDK News)

2. cdk-1.0.x/

* needs QSAR descriptor fixes from trunk/
* needs removal of broken code (IP calculation, structgen code) (***)
* remains to have hydrogen adding and bond deduction problems (****)
* will see End-of-Support this year, unless a release manager steps up

***) Less than 1% of the unit tests will fail after removal of these
unstable bits

****) which is rewritten in trunk/ which does a much better job. This
cannot be fixed in this branch.

Because there are no active release managers at this moment, it is
impossible to give an ETA for release.

Egon

-- 
----
http://chem-bla-ics.blogspot.com/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Cdk-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cdk-user

Reply via email to