> Yes, We saw many reference of code to be fixed on 3.3. Now that some want to
>
> kill 3.3 and directly play with 4.0, the risk of having a 3.x branch
> (the current branch) falling in 'unsupported software land' is VERY HIGH.
This is open source - it's supported as long as some developers are
supporting it :-)
As long as people are using it, the source code and license will keep it
alive.
> Sorry but for now the only existing and used branch is 3.x (3.1 and 3.2b)
> We need a URGENTLY a 3.2 release (with a bug lists) and start the 3.3 beta.
+1
As soon as 3.2 is released I'll make a proposal to freeze 3.3 in 2-4
weeks. Right now 3.3 is almost ready for feature freeze, but we'll need to
merge all the small bug fixes that went into 3.2. ( ready for feature
freeze doesn't mean is ready for release !- it has old and new bugs, but
the major changes are almost done ).
As I said earlier, I don't think we'll need a 3.4 or more changes in
the core very soon - unless somone finds a use case that can't be
implemented with the current architecture or a big performance improvement
that requires a core change. After 3.3 we can have minor ( dot.dot
) releases or just provide updated interceptors.
( that doesn't means 3.x is ended, just that it'll be stable enough as a
framework, and future development can be done without braking backward
compatibility and in separate modules )
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
