Reply to thread

Message

<blockquote data-quote="fforde" data-source="post: 375647" data-attributes="member: 52082">Well as you said, since 0.7 just came out it is a little early to be talking too much about 0.8. Right now we are trying to hammer out all the issues in 0.7 so we can release a 0.7.1 As happy as I am with 0.7.0, it still has some bugs and is not what you would call a &quot;stable&quot; release in the same way that 0.6.6 is. So once we get a 0.7.1 release out the door (which I think will be within a week), we will spend some time planning exactly what will go into 0.8.As for putting filtering in a 0.7 build, I think this is highly unlikely. With our current versioning system, we use the first two digits to indicate a major release with functional changes. The third number (the 1 in 0.7.1) is for bug fixes only. So you will not see new features until 0.8. Don't fret though, the way we number things really has nothing to do with the frequency of releases. A build with new features takes time to put together test and release. This is true whether we call it 0.7.2 or 0.8. Because what's in a name? As you mentioned there are a lot of features tagged for 0.8 on the tracker. The original plan was to do a 0.8 release and then a 1.0 release. But I am really not happy with the length of time between 0.6 and 0.7 so we may be splitting what we have listed in 0.8 into two releases (0.8 and 0.9) so that we can have more frequent feature upgrades.Just be patient though. This is all speculation here, I haven't spent much time planning for 0.8 so it's all still kind of up in the air. We don't want the cart to get in front of the horse, we need to get 0.7 stable before we start moving on.</blockquote>

[QUOTE="fforde, post: 375647, member: 52082"] Well as you said, since 0.7 just came out it is a little early to be talking too much about 0.8. Right now we are trying to hammer out all the issues in 0.7 so we can release a 0.7.1 As happy as I am with 0.7.0, it still has some bugs and is not what you would call a "stable" release in the same way that 0.6.6 is. So once we get a 0.7.1 release out the door (which I think will be within a week), we will spend some time planning exactly what will go into 0.8. As for putting filtering in a 0.7 build, I think this is highly unlikely. With our current versioning system, we use the first two digits to indicate a major release with functional changes. The third number (the 1 in 0.7.1) is for bug fixes only. So you will not see new features until 0.8. Don't fret though, the way we number things really has nothing to do with the frequency of releases. A build with new features takes time to put together test and release. This is true whether we call it 0.7.2 or 0.8. Because what's in a name? As you mentioned there are a lot of features tagged for 0.8 on the tracker. The original plan was to do a 0.8 release and then a 1.0 release. But I am really not happy with the length of time between 0.6 and 0.7 so we may be splitting what we have listed in 0.8 into two releases (0.8 and 0.9) so that we can have more frequent feature upgrades. Just be patient though. This is all speculation here, I haven't spent much time planning for 0.8 so it's all still kind of up in the air. We don't want the cart to get in front of the horse, we need to get 0.7 stable before we start moving on. [/QUOTE]

Verification