I'm (finally) calling the vote on this, here are the results:
2 votes for v2.2 (both binding votes)
6 votes for v3.0 (3 binding votes, 3 non-binding)
It's not "crystal clear", but I feel the general consensus in the
community is that we should make the next stable release v3.0. This
[X] Next stable release should be v3.0.
+1
I'd like to get the API in order.
Thursday, November 4, 2010, 11:23:58 AM, you wrote:
> On 10/29/2010 08:42 AM, Leif Hedstrom wrote:
>> [X] Next stable release should be v3.0.
> -- Leif
> P.s lets break this API once and for all for v3.0 ;)
Yeah, that's why I would prefer 2.2 for the next stable release. We're not
going
On 10/29/2010 08:42 AM, Leif Hedstrom wrote:
[X] Next stable release should be v3.0.
-- Leif
P.s lets break this API once and for all for v3.0 ;)
> [] Next stable release should be v3.0.
+1
Dan M.
I vote for 2.2.
If breaking API & ABI for next stable release then
[+1] Next stable release should be v3.0.
-George
On 10/29/10 7:42 AM, Leif Hedstrom wrote:
> Hi all,
>
> because of incompatibilities between the internal core (which has been
> made 64-bit clean) and the plugin APIs, we will have to make a fe
>
> [+1] Next stable release should be v2.2 (as was planned before the API
> changes)
> [] Next stable release should be v3.0.
>
--
Theo Schlossnagle
http://omniti.com/is/theo-schlossnagle
Hi all,
because of incompatibilities between the internal core (which has been
made 64-bit clean) and the plugin APIs, we will have to make a few
changes to the APIs that breaks API and ABI. It's been suggested that we
should also bump the next stable release to v3.0 for this reason. So,
I'l
