- developers-list - monetdb.org

[Monetdb-developers] Reminder: MonetDB Bug-Etiquette
by Stefan Manegold 19 Jun '06

19 Jun '06

Dear all, since the last MonetDB "BugDay" on Dec 19 2005, many bugs have been reported and fixed. Unfortunately, not all bug reports that have been closed since then have been backed-up by a test script in CVS to verify and monitor to validity of the respective bug fix, as described in the "MonetDB Bug-Etiquette" (cf. one of http://sourceforge.net/mailarchive/forum.php?thread_id=9021727&forum_id=398… http://sourceforge.net/mailarchive/forum.php?thread_id=9021726&forum_id=425… ) According to the "MonetDB Bug-Etiquette", a bug report should (may/must) not be closed without adding a respective test to our test system in CVS. While both the user/submitter that reports the bug and the developer/assignee that fixes it should share the task of "designing" the test and adding it to the test system in CVS, we agreed that the developer/assignee is finally "responsible" that the test is indeed added *before* the bug report is closed. To ensure the stability and correctness of MonetDB and its companions and to avoid that supposedly fixed bug sneak in again unnoticed, I'd like to ask all of you that reported and/or fix any bug(s) since Dec 19 2005 the following favour: Please check all "your" bugs (see * below) since Dec 19 2005, whether a test has been added or not. + If the comments in the bug report are not clear, please check the CVS repository. + If you're a user/submitter and don't know where to look or what to do, please remind the respective developer/assignee of your bug by added a respective comment and re-opening the bug report. + If there is a test, or no test is necessary or feasible, but the bug-report does not mention this clearly, please add a new comment that explains the situation. + If there is no test although there should be one, please re-open the bug report with a respective comment to indicate that a test must be added. As said before, "users/submitters" are welcome to help adding tests, but developers/assignees are finally responsible that the tests are indeed added. Please recall, we plan to release MonetDB 4.12, MonetDB/SQL 2.12 and MonetDB/XQuery 0.12 soon (i.e., before the end of this month), and we all want them to be as stable and "bug-free" as possible...! Feel free to use these channels to comment and/or ask questions. Thank you all very much for your contributions to make MonetDB even better than it already is! Kind regards, Stefan *) To find "your" bugs, just - go to http://sourceforge.net/tracker/?group_id=56967&atid=482468 , - select your username from the list "Assignee:", - or enter your username as "Submitter username (show mine):" (and set "Assignee:" to "Any"), - set "Status:", "Category:" & "Group:" to "Any", - set "Sort By:" to "Open Date" and "Descending", - and click on "Browse". -- | 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 |

1 1

[Monetdb-developers] pathfinder propagations: XQuery_0-12 release branch -> development trunk
by Stefan Manegold 18 Jun '06

18 Jun '06

Dear all, due to the great differences between the two code bases, it is hardly possible to automatically propagate bugfixes from the pathfinder XQuery_0-12 release branch to the pathfinder development trunk. Hence, I kindly ask you to help in doing these propagations by hand as follows: - in case you fix a bug in either branch that also applies to the other branch, please feel free to do the respective propagation (or double check-in) yourself *and* state *clearly* in your check-in message that these two check-ins solve the same problem in both branches! - in case your fix applies to the other branch as well, but you are not able to do the propagation (or double check-in) yourself, please request me to do so by clearly mentioning this request in your check-in message (or even by asking me directly)! - if your fix applies ONLY to the one branch where you check it in, please state clearly that no propagation is required! In case you have checked-in changes to either branch since the creation of the XQuery_0-12 release branch on Monday June 12 2006, but have not propagated it to the other branch yourself, although it should be propagated, please let me know (in detail) which check-ins still need to be propagated and from where to where. Thank you very much for you cooperation! 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 |

1 0

[Monetdb-developers] Pathfinder License update?
by Stefan Manegold 18 Jun '06

18 Jun '06

Hi, I just noticed that the copyright statment in pathfinder/compiler/parser/parser.y (in the development trunk) has been updated by Jens on May 22 2006 as follows: ======== --- compiler/parser/parser.y 14 Mar 2006 22:50:19 -0000 1.36 +++ compiler/parser/parser.y 22 May 2006 15:36:05 -0000 1.37 @@ -22,10 +22,13 @@ * * The Original Code is the Pathfinder system. * - * The Initial Developer of the Original Code is the Database & - * Information Systems Group at the University of Konstanz, Germany. - * Portions created by the University of Konstanz are Copyright (C) - * 2000-2006 University of Konstanz. All Rights Reserved. + * The Original Code has initially been developed by the Database & + * Information Systems Group at the University of Konstanz, Germany + * and is now maintained by the Database Systems Group at the + * Technische Universitaet Muenchen, Germany. Portions created by + * the University of Konstanz and the Technische Universitaet Muenchen + * are Copyright (C) 2000-2005 University of Konstanz and (C) 2005-2006 + * Technische Universitaet Muenchen, respectively. All Rights Reserved. * * $Id$ */ ======== This obviously triggers two questions 1) Should the copyright statement in all pathfinder files be updated accordingly (both in the development trunk and the XQuery_0-12 release branch)? 2) Should we replace "University of Konstanz", "UKO", & "Konstanz" by "Technische Universitaet Muenchen", "TUM", & "Muenchen" in the Pathfinder license http://monetdb.cwi.nl/Development/Legal/PathfinderLicense-1.1/index.html (and hence possible update is to version 1.2)? Any comments are more than welcome! 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 |

3 2

[Monetdb-developers] radix.mx signed/unsigned issue?
by Fabian Groffen 17 Jun '06

17 Jun '06

I just tried to compile MonetDB 4 and hit a compiler warning (error) in radix.mx on a signed/unsigned comparison. I applied the attached patch to make it compiling again, but I'm not sure if this is the intention, as the hard cast might result in the wrong result perhaps? Also, am I the only one experiencing this problem?

1 1

Re: [Monetdb-developers] pathfinder release: bugfixing opportunity
by Stefan Manegold 12 Jun '06

12 Jun '06

[Please use the MonetDB-developers mailing list (monetdb-developers(a)lists.sourceforge.net) for this kind of discussions, and make sure you're subscribed to it (with your current email address). Thanks!] I suggest to not checkin any changes to the XQuery_0-10 stable branch of pathfinder, but to wait until we (Niels, Sjoerd, me) create the new XQuery_0-12 stable branch (together with the new MonetDB_4-12 & SQL_2-12 release branches) early next week. Of course, you're free and welcome to try to compile pathfinder's stable branch (XQuery_0-10) with the current MonetDB 4.11 development trunk to sort-out the problems and start fixing them off-line. The short-term "feature-freeze" for the "intermediate release" applied only to MonetDB & sql; as Peter explained, for pathfinder we plan only porting of XQuery_0-10 to comply/compile with MonetDB 4.11 as well as applying bugfixes (including back-porting bug fixes from XQuery 0.11 as far as necessary/possible). On Thu, Jun 08, 2006 at 12:44:03AM +0200, Jan Rittinger wrote: > > -----Original Message----- > > Hi, > > > > I am not against including the compiler directory, but we > > must be careful > > with: > > - milprint-summer, I think it can't be rolled forward (all > > those tijah changes, and the update changes) > > - update syntax in the parser (it should not be recognized yet) > > - burkowski changes in the parser (may or may not be a > > problem, see below) > > > > You are probably right that removing code probably is as much work as > finding the respective bug fixes. I just skipped through the commit mails of > the last 4 months and looked up checkins that mainly fix bugs. > > So here's a (probably incomplete) list: > milprint_summer.c 182->183, 185->186, 191->192, 208->209, 209->210, > 210->211, 217->218, 219->220, 220->221 > shredder.mx 77->78, 81->82 > pf_support.mx 126->127 > subtyping.c 33->34 > fs.brg 33->34 > > > > > the rule is that if you feel like it and it takes little time, it may be > > welcome. > > > > I identified the following open bugs op the stable branch: > > > > 1447195 PF: crash server with XMark > > 1446426 fn:doc() call in nested element construction fails > > 1339844 PF: A parent step into the void > > 1459974 XQuery: parent-step into all > > 1491723 wrong position numbering in sequence after predicate and: 1410662 PF: tests tests/XQuery/Tests/typing[12].xq fail 1365379 PF: "stable order by" 1351516 PF: attribute after non-attribute content 1207048 XQuery: crashtest those that are "not (yet?) fixable" should be close with the proper comment/explanation. Stefan > > > > will try to compile pathfinder tomorrow and look into these issues. feel > > free to claim ony of these bugs.. > > > > I also identified the following closed bugs on the stable > > branch. They appeared to have been applied only to the HEAD, > > so I backported them to the Stable. This must still be checked: > > > > 1490847 problem with functions in xquery > > QUESTION TO JAN RITTINGER: was this really the small > > change mentioned in the bug report? I applied it. > > it's in the above patch list > > > 1454407 Mserver does not close XQuery sockets > > QUESTION TO NIELS NES: the patch in the bug report was ok? I applied it. > > > > this one I don't know what to do with: > > > > 1463558 wrong result when passing nodelist to function > > QUESTION TO JAN RITTINGER: what was the bug-fix here? > > it's in the above patch list > > > > > QUESTION TO WOUTER: I reported two problems with select-narrow. Can we roll > > forward pf_burk as it is now to the stable, and get those fixes as well as > > the rename? > > > > As the release date is near (I think Niels aims for less than two weeks), > > please treat this with urgency, or do not treat this at all.. > > > > best, > > > > Peter > > > > > > Two bugs that might pop up if we roll forward the MonetDB head (with > > batcache) to Stable pathfinder: > > > > 1499969 PF: tests/XQuery/Tests/typeswitch[34].xq: property errors > > 1499962 PF: XMark Q10: "HASHremove: Assertion `0' failed." > > > > > > > > -----Original Message----- > > From: Jan Rittinger [mailto:rittinge@in.tum.de] > > Sent: 07 June 2006 23:46 > > To: 'Peter Boncz'; wouter(a)holmes.nl; 'Torsten Grust'; 'Jens Teubner'; > > 'Jan Flokstra'; 'Maurice Van Keulen'; 'Wouter Alink' > > Cc: 'Sjoerd Mullender'; 'Stefan Manegold'; Niels.Nes(a)cwi.nl > > Subject: RE: pathfinder release: bugfixing opportunity > > > > > > I have no problem postponing the pf release. > > > > However I think that I (and also others) fixed quite a number of 'important' > > pathfinder bugs. In addition some small but very useful extensions sneaked > > into the code (e.g. we now support all kinds of typeswitches). It would be a > > pitty to ignore them in the coming release. > > > > Is it perhaps possible to include the compiler directory (with small > > adjustments to align it with pf runtime and MonetDB), but leave out changes > > of the runtime? > > > > Jan > > > > > -----Original Message----- > > > From: Peter Boncz [mailto:boncz@cwi.nl] > > > Sent: Wednesday, June 07, 2006 9:41 PM > > > To: wouter(a)holmes.nl; Torsten Grust; Jens Teubner; Jan > > > Rittinger; Jan Flokstra; Maurice Van Keulen; Wouter Alink > > > Cc: Sjoerd Mullender; Stefan Manegold; niels(a)cwi.nl > > > Subject: pathfinder release: bugfixing opportunity > > > > > > Hi, > > > > > > Today we had a MonetDB meeting about the release. We decided > > > to have a release now, but without Pathfinder. > > > > > > For the Pathfinder release with updates, multi-documents and > > > soap the realistic time-frame becomes *september* (well, > > > maybe maybe august), but there will be a feature freeze > > > around SIGMOD (june 25). We anticipate a long testing and > > > debugging stage. Sorry, but this is reality. No SIGMOD release. > > > > > > As MonetDB/SQL and the alpha Monet5 do not want to wait any > > > longer just to roll through the accumulated new features and > > > fixes, there is also an imminent release. As we release > > > always all components to keep compatability and the test web > > > easily manageble in a single Stable an single Current branch, > > > the new release will include the *stable* branch of pathfinder. > > > > > > There will be a (very) small porting effort to make > > > stable-pathfinder work on head-monet. However, one of the > > > tasks ahead for a pathfinder release anyway is bug-fixing. > > > Thus, we can take this opportunity to identify quick-win bugs > > > in pathfinder and release those. We can also look at the bugs > > > fixed in pathfinder in the past period, and ask ourselfves > > > whether rollling them through is useful and little work. > > > > > > I guess the freeze for the direct release is only within > > > days, and I recommend you all not to spend much time on it. > > > At least the new pathfinder will contain the BATuselect fix > > > in the serialization (admittedly not as fast as Jan R.'s > > > current implementation but still better than before). > > > > > > As the experiences with it have been positive, I propose this > > > time to build pathfinder with burkowski enabled. Thus we can > > > point the guy who wants windows with burkowski (and other > > > like him) to the new binary release. Note that the > > > functionality is by default still disabled; you need to set a > > > configuration switch to yes to turn it on. > > > > > > Peter > > > > > > -- | 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 |

2 3

Re: [Monetdb-developers] pathfinder release: bugfixing opportunity
by Wouter Alink (DT) 08 Jun '06

08 Jun '06

Forgot to answer my question: The problem with the stack that was too small has been fixed. The StandOff-joins now increase the stack-size whenever it grows out-of-bound. The StandOff-axes in the stable branch still have two bugs to fix that I know of: - sorting of the final result (with multiple iters, the result is not sorted at the moment). The current work-around is adding a self-step directly after the StandOff-step. - David Ahn mentioned another bug, when nesting 3 for-loops, each using the select-narrow-axis the output is garbage, but I don't know whether this bug is related to the sorting, or perhaps to another part of MonetDB/XQuery. Still have to figure this out. Greetings, Wouter >-----Original Message----- >From: Stefan Manegold [mailto:Stefan.Manegold@cwi.nl] >Sent: Thursday, June 08, 2006 9:42 AM >To: monetdb-developers(a)lists.sourceforge.net >Cc: Wouter Alink (DT); 'Jan Flokstra'; 'Maurice Van Keulen' >Subject: Re: pathfinder release: bugfixing opportunity > > >[Please use the MonetDB-developers mailing list > (monetdb-developers(a)lists.sourceforge.net) for this kind of >discussions, and make sure you're subscribed to it (with your >current email address). Thanks!] > > >I suggest to not checkin any changes to the XQuery_0-10 stable >branch of pathfinder, but to wait until we (Niels, Sjoerd, me) >create the new >XQuery_0-12 stable branch (together with the new MonetDB_4-12 >& SQL_2-12 release branches) early next week. >Of course, you're free and welcome to try to compile >pathfinder's stable branch (XQuery_0-10) with the current >MonetDB 4.11 development trunk to sort-out the problems and >start fixing them off-line. > >The short-term "feature-freeze" for the "intermediate release" >applied only to MonetDB & sql; as Peter explained, for >pathfinder we plan only porting of XQuery_0-10 to >comply/compile with MonetDB 4.11 as well as applying bugfixes >(including back-porting bug fixes from XQuery 0.11 as far as >necessary/possible). > > >On Thu, Jun 08, 2006 at 12:44:03AM +0200, Jan Rittinger wrote: >> > -----Original Message----- >> > Hi, >> > >> > I am not against including the compiler directory, but we must be >> > careful >> > with: >> > - milprint-summer, I think it can't be rolled forward (all those >> > tijah changes, and the update changes) >> > - update syntax in the parser (it should not be recognized yet) >> > - burkowski changes in the parser (may or may not be a >problem, see >> > below) >> > >> >> You are probably right that removing code probably is as >much work as >> finding the respective bug fixes. I just skipped through the commit >> mails of the last 4 months and looked up checkins that >mainly fix bugs. >> >> So here's a (probably incomplete) list: >> milprint_summer.c 182->183, 185->186, 191->192, 208->209, 209->210, >> 210->211, 217->218, 219->220, 220->221 >> shredder.mx 77->78, 81->82 >> pf_support.mx 126->127 >> subtyping.c 33->34 >> fs.brg 33->34 >> >> > >> > the rule is that if you feel like it and it takes little time, it >> > may be welcome. >> > >> > I identified the following open bugs op the stable branch: >> > >> > 1447195 PF: crash server with XMark >> > 1446426 fn:doc() call in nested element construction fails >> > 1339844 PF: A parent step into the void >> > 1459974 XQuery: parent-step into all >> > 1491723 wrong position numbering in sequence after predicate > >and: > >1410662 PF: tests tests/XQuery/Tests/typing[12].xq fail >1365379 PF: "stable order by" >1351516 PF: attribute after non-attribute content >1207048 XQuery: crashtest > >those that are "not (yet?) fixable" should be close with the >proper comment/explanation. > >Stefan > > >> > >> > will try to compile pathfinder tomorrow and look into >these issues. >> > feel free to claim ony of these bugs.. >> > >> > I also identified the following closed bugs on the stable branch. >> > They appeared to have been applied only to the HEAD, so I >backported >> > them to the Stable. This must still be checked: >> > >> > 1490847 problem with functions in xquery >> > QUESTION TO JAN RITTINGER: was this really the small change >> > mentioned in the bug report? I applied it. >> >> it's in the above patch list >> >> > 1454407 Mserver does not close XQuery sockets >> > QUESTION TO NIELS NES: the patch in the bug report >was ok? I applied it. >> > >> > this one I don't know what to do with: >> > >> > 1463558 wrong result when passing nodelist to function >> > QUESTION TO JAN RITTINGER: what was the bug-fix here? >> >> it's in the above patch list >> >> > >> > QUESTION TO WOUTER: I reported two problems with >select-narrow. Can >> > we roll forward pf_burk as it is now to the stable, and get those >> > fixes as well as the rename? >> > >> > As the release date is near (I think Niels aims for less than two >> > weeks), please treat this with urgency, or do not treat >this at all.. >> > >> > best, >> > >> > Peter >> > >> > >> > Two bugs that might pop up if we roll forward the MonetDB >head (with >> > batcache) to Stable pathfinder: >> > >> > 1499969 PF: tests/XQuery/Tests/typeswitch[34].xq: property errors >> > 1499962 PF: XMark Q10: "HASHremove: Assertion `0' failed." >> > >> > >> > >> > -----Original Message----- >> > From: Jan Rittinger [mailto:rittinge@in.tum.de] >> > Sent: 07 June 2006 23:46 >> > To: 'Peter Boncz'; wouter(a)holmes.nl; 'Torsten Grust'; 'Jens >> > Teubner'; 'Jan Flokstra'; 'Maurice Van Keulen'; 'Wouter Alink' >> > Cc: 'Sjoerd Mullender'; 'Stefan Manegold'; Niels.Nes(a)cwi.nl >> > Subject: RE: pathfinder release: bugfixing opportunity >> > >> > >> > I have no problem postponing the pf release. >> > >> > However I think that I (and also others) fixed quite a >number of 'important' >> > pathfinder bugs. In addition some small but very useful extensions >> > sneaked into the code (e.g. we now support all kinds of >> > typeswitches). It would be a pitty to ignore them in the >coming release. >> > >> > Is it perhaps possible to include the compiler directory >(with small >> > adjustments to align it with pf runtime and MonetDB), but >leave out >> > changes of the runtime? >> > >> > Jan >> > >> > > -----Original Message----- >> > > From: Peter Boncz [mailto:boncz@cwi.nl] >> > > Sent: Wednesday, June 07, 2006 9:41 PM >> > > To: wouter(a)holmes.nl; Torsten Grust; Jens Teubner; Jan >Rittinger; >> > > Jan Flokstra; Maurice Van Keulen; Wouter Alink >> > > Cc: Sjoerd Mullender; Stefan Manegold; niels(a)cwi.nl >> > > Subject: pathfinder release: bugfixing opportunity >> > > >> > > Hi, >> > > >> > > Today we had a MonetDB meeting about the release. We decided to >> > > have a release now, but without Pathfinder. >> > > >> > > For the Pathfinder release with updates, multi-documents >and soap >> > > the realistic time-frame becomes *september* (well, maybe maybe >> > > august), but there will be a feature freeze around SIGMOD (june >> > > 25). We anticipate a long testing and debugging stage. >Sorry, but >> > > this is reality. No SIGMOD release. >> > > >> > > As MonetDB/SQL and the alpha Monet5 do not want to wait >any longer >> > > just to roll through the accumulated new features and >fixes, there >> > > is also an imminent release. As we release always all components >> > > to keep compatability and the test web easily manageble in a >> > > single Stable an single Current branch, the new release will >> > > include the *stable* branch of pathfinder. >> > > >> > > There will be a (very) small porting effort to make >> > > stable-pathfinder work on head-monet. However, one of the tasks >> > > ahead for a pathfinder release anyway is bug-fixing. >> > > Thus, we can take this opportunity to identify quick-win bugs in >> > > pathfinder and release those. We can also look at the bugs fixed >> > > in pathfinder in the past period, and ask ourselfves whether >> > > rollling them through is useful and little work. >> > > >> > > I guess the freeze for the direct release is only within >days, and >> > > I recommend you all not to spend much time on it. >> > > At least the new pathfinder will contain the BATuselect >fix in the >> > > serialization (admittedly not as fast as Jan R.'s current >> > > implementation but still better than before). >> > > >> > > As the experiences with it have been positive, I propose >this time >> > > to build pathfinder with burkowski enabled. Thus we can >point the >> > > guy who wants windows with burkowski (and other like him) to the >> > > new binary release. Note that the functionality is by default >> > > still disabled; you need to set a configuration switch to yes to >> > > turn it on. >> > > >> > > Peter >> > > >> > > > >-- >| 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 | >

1 0

[Monetdb-developers] pathfinder release: bugfixing opportunity
by Peter Boncz 07 Jun '06

07 Jun '06

LS, Today we had a MonetDB meeting about the release. We decided to have a release now, but without Pathfinder. For the Pathfinder release with updates, multi-documents and soap the realistic time-frame becomes *september* (well, maybe maybe august), but there will be a feature freeze around SIGMOD (june 25). We anticipate a long testing and debugging stage. Sorry, but this is reality. No SIGMOD release. As MonetDB/SQL and the alpha Monet5 do not want to wait any longer just to roll through the accumulated new features and fixes, there is also an imminent release. As we release always all components to keep compatability and the test web easily manageble in a single Stable an single Current branch, the new release will include the *stable* branch of pathfinder. There will be a (very) small porting effort to make stable-pathfinder work on head-monet. However, one of the tasks ahead for a pathfinder release anyway is bug-fixing. Thus, we can take this opportunity to identify quick-win bugs in pathfinder and release those. We can also look at the bugs fixed in pathfinder in the past period, and ask ourselfves whether rollling them through is useful and little work. I guess the freeze for the direct release is only within days, and I recommend you all not to spend much time on it. At least the new pathfinder will contain the BATuselect fix in the serialization (admittedly not as fast as Jan R.'s current implementation but still better than before). As the experiences with it have been positive, I propose this time to build pathfinder with burkowski enabled. Thus we can point the guy who wants windows with burkowski (and other like him) to the new binary release. Note that the functionality is by default still disabled; you need to set a configuration switch to yes to turn it on. Peter

1 0

[Monetdb-developers] MonetDB release meeting
by Niels Nes 06 Jun '06

06 Jun '06

MonetDB developers On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting. Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work. Niels -- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes(a)cwi.nl

8 15

[Monetdb-developers] feature freeze
by Peter Boncz 05 Jun '06

05 Jun '06

Niels, Feature freeze? One little problem: none of the XQuery targets is met (updates, soap, multi-document). So what do you (or you talk about "we") want to release? In my opinion - but correct me if I'm wrong - the goal of the release is the new XQuery version that brings updates. Thus I am against a feature freeze on monday. Creating the branch now will just create propagation overhead. It will take al least another 3 weeks until the basic features will be implemented, after that we have to go into a testing and packaging period still. Of course one should try to impose limits and milestones. Or even scrap goals if the milestones are never made. But in this case there is clear progress being made. Peter

2 1

[Monetdb-developers] monetdb feature freeze
by Niels Nes 02 Jun '06

02 Jun '06

MonetDB developers As you probably all know last thursday june 1 was the planned feature freeze date. Because of many reasons we didn't directly create the seperate cvs branches to really enforce the freeze. But we are serious, so we are about create these branches soon. Current planning is to create these on tuesday morning. Afcouse during the branch creation its better not to checkin changes. Therefor I hope everybody cleans up its checkout versions and checks in those changes which should end up in the to be released version before monday evening. The version of monday night (amsterdam time) marks, which features will be in the release. Niels Nes -- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes(a)cwi.nl

1 0