we discussed shortly about the forthcoming release
the release early or release often might not always be good
it can be either a good or a bad marketing weapon
testing code before release is something that you don't want to do generally
and good testing frameworks may not be easy at all to setup depending on the
project.
However here what we can do for the next release:
1- on corelinux (tarball + packages):
* hans work on semaphore (it is always good to have new features)
* compilation fixes, c++ correctness
* macro changes, will break existing codes
* new -dbg package for debugging purpose
2- on clfw (tarball)
* preview technology for the LibraryLoader
comments? other stuff to add?
my best regards
C.
--
Christophe Prud'homme |
MIT, 77, Mass Ave, Rm 3-243 | In theory, theory and practice
Cambridge MA 02139 | are the same. In practice they
Tel (Office) : (00 1) (617) 253 0229 | are different.
Fax (Office) : (00 1) (617) 258 8559 |
http://augustine.mit.edu/~prudhomm |
Following the hacker spirit
|
