While a little premature, I have a specific proposal for an early 1.0 release. In fact, the shortly to be introduced 0.9.5 release finally includes all of the functionality I originally envisioned for 1.0, which is why this message is here.
In particular, I wish to split Common C++ into two packages; "Common C++" proper, and a new "Common C++ extras" package.
The extras package would hold any code not yet ready for the full or stable production "release", or that is still in flux/likely to be redefined substancially later.
In particular, the extras "package" would likely include the Bayonne script engine, the incomplete math classes, and the anemic "win32" development tree. This would clearly mark these components as not being "fully developed" as of yet, and still allow the rest of the package, which is now very frozen and stable, to be able to be distributed as a 1.0 package.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While a little premature, I have a specific proposal for an early 1.0 release. In fact, the shortly to be introduced 0.9.5 release finally includes all of the functionality I originally envisioned for 1.0, which is why this message is here.
In particular, I wish to split Common C++ into two packages; "Common C++" proper, and a new "Common C++ extras" package.
The extras package would hold any code not yet ready for the full or stable production "release", or that is still in flux/likely to be redefined substancially later.
In particular, the extras "package" would likely include the Bayonne script engine, the incomplete math classes, and the anemic "win32" development tree. This would clearly mark these components as not being "fully developed" as of yet, and still allow the rest of the package, which is now very frozen and stable, to be able to be distributed as a 1.0 package.