On Tue, Jan 17, 2006 at 09:07:29AM +0100, Fabian Groffen wrote:
- We decided that we would not do these kinds of extras.
It was in before we decided that (and hence before the original freeze date). as far as I recall, we hadn't decided, yet, to actively "throw it out". (Hence my question...)
- Since Wouter just checked it in, there is no testweb coverage (yet). - Changing plans to now advertise Burkowski steps, means you also have to reconsider SOAP to be fair to others.
SOAP is partly in, but AFAIK far from finished; we will not announce it, but removing code traces is impossible (as opposed to the Burkowski stuff, which is nicely tagged in CVS (I tagged part one, Wouter tagged part two). SOAP development currently proceeds on a branch and will be merged in and released with the next release.
A big "no-go" from me. We should freeze the sources, not add all kinds of things at the very last moment. Why are the sources not frozen yet?
well, kind of my decision/fault, since the void/oid changes/fixes are still pending. to reduce (my) work, a feature freeze for me coinsides with making a new stable branch; doing this before the void/oid changes/fixes are in would require extra propagation... (btw, a freeze on Friday Jan 13 would only have kept your latest JDBC changes out of the release ... ;-))
(Does this list also know the reason?)
well, now yes ;-) (sorry for the delay...)
Many people are waiting for an updated snapshot of MonetDB. Why delay and delay and delay. If you want to have these options, just release more often. IMHO the releases take far too much human resources, and should be much more relaxed. If you haven't got it in front of you on the table, tested and all, then it's simply not in. Not every release must be an eye-opener for the world, people are just waiting on a new version which fixes all of their bugs. They are waiting since August 1, 2005.
Agree (almost) completely. The point/problem is, that somehow all of us want (in one way or an other) "perfect" releases, both from the users' and from the developers' point of view (some major contributions to "sell" is, all bugs fixed, better packaging, better/more documentation, better/simpler compilation, more/better testing, ...), and all only start thinking (and acting) about this, once release "plans" become more concrete, and that happens only shortly before a (planned) release.... maybe too many (contradicting?) optimization targets? maybe too many "cooks"??? Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |