Le dimanche 06 février 2011 15:36:35, Samuel Mimram a écrit :
> Hi,
Howdy all!
Sorry for my silence about this lately.
First and foremost:
http://www.rastageeks.org/fun.html
That ridiculous statement made, I have to say that I am leaning towards Sam's
position.
More precisely, I totally agree on the important work that the opportunity of
a release triggers. On the other hand, I do not like when I have to advise to
use SVN often on the mailing list. This is particularly true when the new
release introduces important changes in the language..
I would like to mention, though, that releasing 1.0 beta was very helpful in
providing a static code base clearly identified to push towards 1.0. But since
then we have fixed enough bugs and changed enough things in the SVN up to the
point where we have to advise SVN a lot of times..
We do not have to release a final 1.0, though: we could have a second beta and
package it for debian and ubuntu.
I think my personal line is about io stuff: this should have been looked before
-- and I think I should do it.
If io/ code is merged soon then I would see not major issue preventing a 1.0
release. (well, merging v4l would be good too..).
Romain
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Savonet-devl mailing list
Savonet-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-devl
