An alternative would be to stay on board with the main controller and push it out as the big 2.0
Why?... 1) People that are riding the edge to get that all important functionality will be on the nightly build anyways. Hell, indexed tags are enough to get a lot of them stepping up to the plate let alone something big like the sub-app support. 2) But for the people that rely on releases, get the in-the-face notion from the full digit update that it's a big step forward and should do some compatibility checks on their own software before jumping in with both feet. From a marketing point of view... - Point updates tend to say that it will work as you expect it, minor updates. - Whole number updates tend to say that something really cool just happened, possibly a paradigm change so there may be backwards compatibility changes. Every good software production tries to keep some backwards compatibility, but sometimes it not 100% certifiable. This is one of those times. IMO, I think that we can say it with marking BS rather than having to spend more hours at the keyboard covering all coding angles. This is certainly the easiest way out coding wise, and it says it all to our users as to how they should approach it. What other structure changes are on the board that are likely to be bigger than this to warrant putting _this_ off to take the full digit release?... Arron. Ted Husted wrote: >[ a lot of stuff ] > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
