Hi, > [snip] > > Inside OpenSG no code at all, outside quite some. The main problem is > > not so much the code change. As said above, tracking diverging 1.x and > > 2.x branches is the really painful part. I tried that one already on a > > non trivial code base and it wasn't that much fun ;-). > > > > I agree with this statement and it scares me quite a bit. The 1.x and > 2.0 code branches are diverging and I don't see an end to it in sight. > IMHO we have to find a way to end the 1.x series otherwise the 2.0 > series will never really get going.
>From a user-only perspective: Get this 1.8 out there and forget about it, I don't see why 1.8 has not been released yet, is there development going on for 1.8 anyway? I just see "minor" fixes on the commit list..... > Am I the only one that sees this as a big problem for the project? > > Is there a plan for ending the 1.x branch and transitioning to 2.0? Get it done as soon as possible... At least if you're planning to release 2.0 in August.... (very optimistic IMHO). Hopefully I didn't offend anybody, and consider that this is an opinion of a person not involved in the development and a total ignorant concerning OpenSG 2.0 ... :-O Regards & continue the good work, Toni ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
