> I think it's simply because there are/were different views on what is > considered new features and what is considered a fix. > > There are new things since 1.0.2 that fix certain user's specific problems, > but they fix the problem by adding functionality. :) It is difficult to say > where the bordeline lies between the two. > > Eg: I want to have a stab at controlling fetchSize this week and this has > already > been "cheered for" on both 1.0.x and 1.1 - new functionality one can argue, > but a usable feature solving a real-world problem without beeing a big or > intrusive > change for 1.0.4. > > Personally I am schizofrenically +1 for both making and not making such a > change on the branch. It's "fixing" OutOfMemory with PostgreSQL but is > "new functionality" in the configuration area. :) > > But I think Jakob's call for a 1.1 pre-release will make these sort of > discussions redundant, when release-focus is moved from branch to trunk.
Right, once a first 1.1 version is out we could adopt a voting-scheme for things that can be seen as new features in the 1.0, e.g. the fetchSize attribute. Then we can always decide whether to add it to the 1.0 or not. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
