Hi, On Tue, 2007-06-05 at 17:13 -0500, Daniel E. Shipton wrote: > > >> [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. > > Diverging may be an understatement.
It is not as bad as it sounds. > > >>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..... > > I don't see many of these minor fixes making their way over to 2.0 > which concerns me. Which in particular ??, we do not merge on a regular basis but usually all these minor fixes get pulled over once we merge (as far as they apply). Also some things inside 1.x need to be redesigned before they end up in 2.x as the current 1.x implementation is more than ugly ;-). > > > > Well said. I don't see why 1.8 is not release yet either. It has been > > stable forever and should be in maintenance mode by now. > > > > What is holding up the release of 1.8? > Is 1.8 ready to ship in a week, month, year? Is there some hold up > that is not apparent to everyone? see down below > > > > > >> 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). > > > > Note: I don't speak for the OpenSG team. I may commit code once in a > > while, but I am not a core developer. I proposed August as a time for > > an alpha 2.0 because we are already using it and it seems at least alpha > > quality to me. ;) Kind of agree, but there is a roadblock ;-(, the pieces that are there are close to alpha, there should be some cleanup but August could be a reasonable time frame for an alpha iff we finally manage decide on the pointer stuff ASAP. Both implementations are there and running. Dirk wanted to work on it a while back but I don't have any feedback on the status right now. We both are in favor of using plain C pointers (IIRC) the only thing we could not really agree on was the use of RefPointer. I'm more cautious when using them internally and Dirk is more in favor of using them internally. But actually I'm ok with both as long as the performance does not decrease and I don't have to implement them ;-). So if we agree on C pointer I could go ahead and remove the fcptr pointer code along with the mixin cleanup I did a while back. Once we have this part out of the way we can go ahead and look into the ref pointer problem. >From there it should be downhill towards a 2.x alpha ;-) > I am also not a core developer but some guidance may be needed to herd > the available developers and move the project forward. s***, I am a core developer ;-). But 99% of my time I'm concerned about 2.x so I basically don't do any 1.x development anymore and intentionally left the 1.x release to Dirk and Andreas (sorry ;-)). So for me 1.x is already dead and buried and I did not follow the discussion why 1.8 was not released yet, so I have no idea why it is delayed. regards, gerrit ------------------------------------------------------------------------- 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
