- announce-list - monetdb.org

[Monetdb-announce] New (pre-) release "MonetDB_4-3-16"
by Stefan.Manegold＠cwi.nl 09 Apr '04

09 Apr '04

Hello MonetDB users and developers, finally, the (pre-) release "MonetDB_4-3-16" is available on SourceForge (http://sourceforge.net/projects/monetdb/). Changes since the last release candidate "MonetDB_4-3-16_rc06" are mainly bug fixes and performance improvements; for details, see the change log in the monetdb-changelogs mailing list (http://lists.sourceforge.net/lists/listinfo/monetdb-changelogs). Please use the new release and report any related bugs or problems through the SourceForge bug tracker (https://sourceforge.net/tracker/?group_id=56967&atid=482468). Downloads ========= [ For the time being, only the (generic) souce distribution and the binary ] [ distribution (rpm) for Linux are available. ] [ The binary distribution for Windows will follow on Tuesday, April 13. ] MonetDB-*-4.3.16-1_*.i686.rpm ----------------------------- These rpm's contain the binary distribution for Linux. The *RedHat* rpm's were built on a RedHat-9 system and the *SuSE* rpm's were built on a SuSE-8.1 system; however, both should work on other Linux distributions as well (unless there are incompatibilities with dynamically linked system libraries...). While the MonetDB-client-4.3.16-1_*.i686.rpm can be installed stand-alone, the MonetDB-server-4.3.16-1_*.i686.rpm requires the matching MonetDB-client-4.3.16-1_*.i686.rpm to be installed as well. To develop your own add-on modules, you additionally need to install the MonetDB-devel-4.3.16-1_*.i686.rpm. MonetDB-4.3.16.tar.gz --------------------- This is a gzip'ed tar file containing the source code; read HowToStart or HowToStart-Win32.txt for build instructions. Mknife-1.0.16.jar ----------------- Mknife is a 'Swiss army knife' GUI to ease the interaction with a running MonetDB server. See http://monetdb.cwi.nl/GetGoing/Usage/Mknife/ for details. CVS update ========== If you are already using the release (candidate) branch "MonetDB_4-3-16" from CVS, simply run "cvs update -dP" to update your code to this new release version. If you are using any other CVS version, you can either run "cvs update -dP -rMonetDB_4-3-16_release" to get this very release, or "cvs update -dP -rMonetDB_4-3-16" to get the most recent version in the release branch. The difference is, that via the first option, you are "stuck" with this very release, i.e., future "cvs update" (without "-r..." or "-A") will not change your checked-out version; via the second option, however, future "cvs update" will get you again the latest version in the release branch. Happy Easter! 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-announce] New release candidate "MonetDB_4-3-16_rc06"
by Stefan.Manegold＠cwi.nl 31 Mar '04

31 Mar '04

Hello MonetDB users and developers, a new release candidate "MonetDB_4-3-16_rc06" is available on SourceForge (http://sourceforge.net/projects/monetdb/). Changes since the last release candidate "MonetDB_4-3-16_rc04" are mainly bug fixes and performance improvements; for details, see the change log in the monetdb-changelogs mailing list (http://lists.sourceforge.net/lists/listinfo/monetdb-changelogs). Please use the new release candidate and report any related bugs or problems through the SourceForge bug tracker (https://sourceforge.net/tracker/?group_id=56967&atid=482468). Downloads ========= MonetDB-Setup-4.3.16_rc06.zip ----------------------------- This is a zip file which contains a file Setup.exe which is the Windows installer. Extract the zip file somewhere, and start Setup.exe to install MonetDB. This installer also contains the SQL frontend which is automatically installed. Once installed, you can find shortcuts to the SQL server and SQL client in the Start menu. [ The following packages do not (yet) include the SQL frontend. ] [ Respective packages for the SQL frontend will be available soon. ] MonetDB-*-4.3.16_rc06-1.*.rpm ----------------------------- These rpm's contain the binary distribution for Linux. The *.athlon.rpm were built on a RedHat-9 system and the *.i686.rpm were built on a SuSE-8.0 system; however, both should work on other Linux distributions as well (unless there are incompatibilities with dynamically linked system libraries...). The *.athlon.rpm should also work on a i686 machine, and vice versa, though you might need to overrule rpm's architecture check using "--ignorearch". While the MonetDB-client--4.3.16_rc06-1.*.rpm can be installed stand-alone, the MonetDB-server-4.3.16_rc06-1.*.rpm requires the matching MonetDB-client--4.3.16_rc06-1.*.rpm to be installed as well. To develop your own add-on modules, you additionally need to install the MonetDB-devel-4.3.16_rc06-1.*.rpm. MonetDB-4.3.16_rc06.tar.gz -------------------------- This is a gzip'ed tar file containing the source code; read HowToStart or HowToStart-Win32.txt for build instructions. CVS update ========== If you are already using the release candidate branch "MonetDB_4-3-16" from CVS, simply run "cvs update -dP" to update your code to this new release candidate version. If you are using any other CVS version, you can either run "cvs update -dP -rMonetDB_4-3-16_rc06" to get this very release candidate, or "cvs update -dP -rMonetDB_4-3-16" to get the most recent version in the release candidate branch. The difference is, that via the first option, you are "stuck" with this very release candidate, i.e., future "cvs update" (without "-r..." or "-A") will not change your checked-out version; via the second option, however, future "cvs update" will get you again the latest version in the release candidate branch. Enjoy! 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-announce] Two new MonetDB mailing lists @ SF
by Stefan.Manegold＠cwi.nl 31 Mar '04

31 Mar '04

Hi MonetDB'ers, two new mailings for the MonetDB project have been created at SourceForge: - monetdb-developers (http://lists.sourceforge.net/lists/listinfo/monetdb-developers) is meant to be a new communication channel for all development related issues. Using the mailing list shall save us from the need to use and maintain lengthy To-/Cc-lists and allows a broader community to keep track of what developers currently take about. Please do use this list as of now. - monetdb-changelogs (http://lists.sourceforge.net/lists/listinfo/monetdb-changelogs) "the system" will regularly (e.g., on a weekly basis) post digests of MonetDB checkin messages (excluding "diffs"), hence, it provides a "low-traffic" alternate to the regular checkin lists for those of you, who want to stay up-to-date with recent changes of the code base. Additionally, "major" change logs between release( candidate)s will be posted here. Enjoy! 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-announce] MonetDB CVS check-in guidelines
by Stefan.Manegold＠cwi.nl 15 Mar '04

15 Mar '04

[ My apologies for the partly redundant/overlapping recipient list. ] [ I wanted to be sure, that "all of you" receive this mail ... ;-) ] Dear (potential ;-) MonetDB developers, to minimize maintenance cost/overhead and avoid conflict/inconsistencies, we (the "core developers") decided to implement the following guidelines for check-ins to the MonetDB CVS repository on SourceForge. These guidelines are active until they are recalled. - All bug fixes go *only* to the release branch ("MonetDB_4-3-16"). - Bug fixes get into the main/head/development branch *only* by being propagated from the release branch. - I (i.e., *only* I ;-) will take care of propagating bug fixes back from the release branch to the main/head/ development branch on a regular basis --- most probably once a day. - "New features" go *only* to the main/head/development branch and are *never* propagated to the release branch. - All check-ins to the main/head/development branch and considered "new features", and hence, never make it into the release branch. Thank you very much in advance for your 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-announce] New release-candidate branch "MonetDB_4-3-16" (re-sent)
by Stefan.Manegold＠cwi.nl 10 Mar '04

10 Mar '04

[ Sorry for posting this message a second time, but since I haven't see the ] [ first version neither on my mail box nor on the respective archive on SF, ] [ I need to test, whether the mailing list is working at all... ] Dear MonetDB users and developers, I just created the new release-candidate branch "MonetDB_4-3-16". The current version is tagged as "MonetDB_4-3-16_rc04". All users are highly advised (actually "requested" ;-) to use the "MonetDB_4-3-16" branch as of now. To do so, check-out or update from CVS with "-rMonetDB_4-3-16", or download one of the prepared source and binary packages from SourceForge: - a source distribution (.tar.gz) - 3 RPMs (server, client, devel) - a Windows installer (.zip file, extract and execute the Setup.exe) Please do not hesiate to ask for support and report bugs, preferably via the bug tracing system at SF (http://sourceforge.net/tracker/?group_id=56967&atid=482468) or via email to monet(a)cwi.nl; however, please always state clearly which version of MonetDB you are using (as the Mserver tells you at startup)! Any support for the now obsolete "Monet_4-3-14" will stop as of now. All bug fixes (and only these!) on MonetDB are bound to go to the new release-candidate branch ("MonetDB_4-3-16"), first, and then to be propagated to the main branch. All new features are bound to go to the main branch (and only there!). This release-candidate branch will become the new stable/release branch within the next 5 weeks. At least until then, this release-candidate branch will be tested every night. All add-on modules that are tested every night will be tested with this release-branch, *only*, unless the very maintainer(s) of any add-on module request differently. I'll try to also test the main/development branch every night, but surely only MonetDB, no add-on modules. As usually, any (constructive;-) comments and feedback are more than welcome! Enjoy! 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-announce] New release-candidate branch "MonetDB_4-3-16"
by Stefan.Manegold＠cwi.nl 10 Mar '04

10 Mar '04

Dear MonetDB users and developers, I just created the new release-candidate branch "MonetDB_4-3-16". The current version is tagged as "MonetDB_4-3-16_rc04". All users are highly advised (actually "requested" ;-) to use the "MonetDB_4-3-16" branch as of now. (check-out or update from CVS with "-rMonetDB_4-3-16", source and binary packages will follow tomorrow.) Please do not hesiate to ask for support and report bugs, preferably via the bug tracing system at SF (http://sourceforge.net/tracker/?group_id=56967&atid=482468) or via email to monet(a)cwi.nl; however, please always state clearly which version of MonetDB you are using (as the Mserver tells you at startup)! Any support for the now obsolete "Monet_4-3-14" will stop as of now. All bug fixes (and only these!) on MonetDB are bound to go to the new release-candidate branch ("MonetDB_4-3-16"), first, and then to be propagated to the main branch. All new features are bound to go to the main branch (and only there!). This release-candidate branch will become the new stable/release branch within the next 5 weeks. At least until then, this release-candidate branch will be tested every night. All add-on modules that are tested every night will be tested with this release-branch, *only*, unless the very maintainer(s) of any add-on module request differently. I'll try to also test the main/development branch every night, but surely only MonetDB, no add-on modules. As usually, any (constructive;-) comments and feedback are more than welcome! Enjoy! 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 |

2 1

[Monetdb-announce] RFC: Preparing a new "stable" MonetDB 4.3.16
by Stefan.Manegold＠cwi.nl 03 Mar '04

03 Mar '04

Dear MonetDB user and developers, given the growing MonetDB community, it becomes ever more important to have a proper version management for and properly made "stable" versions of MonetDB. The purpose of this mail is to (1) initiate a new approach that tries to find a compromise between "user needs" and available "developer and maintainer man-hours"; and (2) ask for feedback, discussion, and ideas about this approach that will hopefully lead to an "even better" solution ;-) Well, here are my late-night ideas: To have a common starting point, I just tagged the most recent CVS version of MonetDB as "MonetDB_4-3-16_rc01", i.e., it's supposed to be the first release candidate for the to-be-made new "stable" MonetDB-4.3.16. I'd like to encourage all MonetDB "users" of you to spend some (spare?) time to download this version, and test it with you usual MonetDB tasks. Well, as usual, there is of course now "guarantee", hence, it might be a good idea to have this version running next to your current "stable"/"production" version of MonetDB, rather than immediately replacing the latter. Yes, there will be things that work differently, or do not work at all (without any changes on your side). I kindly ask you, to report all these issues to us "developers", preferably as bug reports and feature requests via SF or simply via mail to monet(a)cwi.nl. Since we ("developers") have no complete overview of your ("users") local setting, we need your help in making the next stable version of MonetDB both stable and convenient to use for you. Moreover, this kind of "beta-testing" extends our usual automatic testing that we do every night anyway. So far, we can only say that a stable version is/was "stable" with respect to the test set we use for automatic testing (cf. http://monetdb.cwi.nl/TestWeb). However, not all aspects of MonetDB are covered by the tests, yet(?). We will added as many of your reports as possible to the test set, hence (most of) the "beta-test" will become automatic in the future. However, various scenarios simply cannot be reproduced in the automatic testing, e.g., as they require a setup that is simply too big or runs too long. Hence, please do help us, and you'll (hopefully) eventually be rewarded with a new "stable" MonetDB that deserves this attribute from the very day of its birth. Now to you fellow developers and maintainers ;-) Next to helping out in fixing the floods of bugs that will be sent towards us after the request above, my major question is about your plans for current and future developments: Which new features should be in 4.3.16 and which can/should better wait until thereafter. The main reason for this question is, that we should provide clear cuts to the users, which features are in which version of MonetDB. Timing: Given some "external constraints" (;-), I plan to release the "user-tested" ("user-approved"?) MonetDB 4.3.16 no later than April 14 2004, i.e., in about 6 weeks. So please keep this in mind when planning your contributions in the above scenario. During these 6 weeks, we will tag further release candidates and ask users for help in testing them (at least on all those tests/scenarios we could not add to test automatic test set for whatever reason). Ok, this is my first late-night shot about this issue. As I said, it's just a proposal. Nothing's carved in stone, yet (apart from this mail and the CVS tag ;-), so please do comment on this and state your opinion, what ever it might be! Thank you very much in advance! Good night, 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-announce] MonetDB Test-Web has moved
by Stefan.Manegold＠cwi.nl 10 Dec '03

10 Dec '03

Hi, the MonetDB Test-Web has moved from http://monetdb.cwi.nl/intern/ to http://monetdb.cwi.nl/TestWeb/ Regards, Stefan PS: Some of you are (still?) not interested in announcements about MonetDB !? ;-) (cf., http://lists.sourceforge.net/lists/listinfo/monetdb-announce) -- | 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-announce] MonetDB-4.3.14c source archives available at SourceForge
by Sjoerd Mullender 06 Nov '03

06 Nov '03

The source for the 4.3.14c release of MonetDB is now available as tar and zip files from SourceForge. Please visit the MonetDB project page at http://sourceforge.net/projects/monetdb/ where you will find a link to the download area.

1 0

[Monetdb-announce] Updated (reasonably) stable (pre-)release: Monet_4-3-14c
by Stefan.Manegold＠cwi.nl 06 Nov '03

06 Nov '03

Updated (reasonably) stable (pre-)release: Monet_4-3-14c ======================================================== Dear MonetDB-Users, I just applied all recent changes from the main (development) branch of MonetDB to the "Monet_4-3-14" stable branch. This updated stable version is now called "MonetDB 4.3.14c". For details on how stable it indeed is, have a look at our "Test-Web" at http://monetdb.cwi.nl/intern/ and/or browse the open bug-reports on SourceForge at http://sourceforge.net/projects/monetdb/ If you do already use "MonetDB 4.3.14" (i.e., the "Monet_4-3-14" stable branch), simply run cvs update -dP in your top-level source directory to get the new version. Users of all older version should eventually step-over to "MonetDB 4.3.14c"; simply run cvs update -dP -rMonet_4-3-14 in your top-level source directory to get the new version. Please let me know in case you need help with this. To checkout the new branch from scratch, do cvs -z3 $YOURCVSROOT co -rMonet_4-3-14 MonetDB where YOURCVSROOT="-d:pserver:anonymous@cvs.monetdb.sourceforge.net:/cvsroot/monetdb" if you're using anonymous pserver checkout, or YOURCVSROOT="-d:ext:developername@cvs.monetdb.sourceforge.net:/cvsroot/monetdb" if you have a sourceforge account to checkout via ssh. Development continues on the main branch, which still carries the version number "4.3.15". As usually, significant bug fixes should go to both, the main branch and the Monet_4-3-14 branch. Changelog/Benefits ------------------ The main reason for this updated stable release are a bunch of bug fixes that have been implemented during the last four weeks. Most of them should not affect users in any other way than that MonetDB now compiles and runs better on all supported platforms. For details have a look at the "change logs" at http://monetdb.cwi.nl/intern/, or contact the respective developers. Two changes might affect your applications using the C-API of MonetDB: =================================================================== 2003/10/28 - sjoerd: src/common/stream.mx src/gdk/gdk_atoms.mx src/gdk/gdk_bbp.mx src/gdk/gdk_storage.mx src/gdk/gdk_utils.mx src/mapi/mapi.mx src/mapi/clients/C/Mapi.mx src/modules/contrib/vector.mx src/modules/contrib/wisc.mx src/modules/plain/ascii_io.mx src/modules/plain/enum.mx src/modules/plain/kernel.mx src/modules/plain/streams.mx src/monet/monet_client.mx src/monet/monet_deparse.mx src/monet/monet_parse.mx src/monet/monet_process.mx Changed interface to streams: If you have a stream *s, you now have to call the following functions to read/write/etc with the stream: stream_read(s, buf, elmsize, cnt) stream_write(s, buf, elmsize, cnt) stream_close(s) stream_destroy(s) stream_error(s) stream_flush(s) stream_name(s) stream_errnr(s) stream_byteorder(s) instead of the old way which was s->read(s, buf, elmsize, cnt) s->write(s, buf, elmsize, cnt) s->close(s) s->destroy(s) s->error(s) s->flush(s) s->name s->errnr s->byteorder The advantage of this change is that you only need to specify the stream value once (elimintating potential, hard-to-find bugs); the stream implementation can be completely hidden. If you need the old interface, uncomment the define for BACKWARD_COMPATIBLE_STREAM_DEFINITION in src/common/stream.mx. =================================================================== 2003/10/31 - sjoerd: src/mapi/clients/C/Mapi.mx src/mapi/clients/C/MapiClient.mx src/mapi/examples/C/sample0.c src/mapi/examples/C/sample1.c src/mapi/examples/C/sample2.c src/mapi/examples/C/sample3.c src/mapi/examples/C/sample4.c src/mapi/examples/C/smack00.c src/mapi/examples/C/smack01.c Changed API of mapi_connect. Before the prototype was Mapi mapi_connect(char *host, char *username, char *password, char *lang) where host is actuall host:port; not the prototype is Mapi mapi_connect(char *host, int port, char *username, char *password, char *lang) where host is just host and the port is a separate parameter. The sample scripts now expect a separate host and port argument (in as far as they expected a combined host:port argument). =================================================================== Caveat ------ Martin's *new* MAPI functionality in not exhaustively tested, yet, and hence not guaranteed to work. However, all old functionality *should* work as expected. Extra modules and front ends ---------------------------- With "MonetDB 4.3.14c" and "MonetDB 4.3.15" being identically right now, the HEAD version of all extra modules and front ends that are publicly available (sql, template) or used within CWI, only, (xml, gis, acoi, misq, times100, playpen, pruning) (are supposed to) compile with both. This might change as soon as the is need to apply changes in the main (development) branch of MonetDB that will break the compatibility. Such changes should hence not be propagated to the stable "Monet_4-3-14" branch (unless *all* extra modules and front ends are immediately updated accordingly). Likewise, any no changes to the extra modules and front ends that break compatibility with "MonetDB 4.3.14c" should be checked in to their respective main branch, unless all developers of that extra module or front end agree on abandoning compatibility with "MonetDB 4.3.14c" and moving forward to "MonetDB 4.3.15". Testing ------- The daily testing will continue as is: The main branches (MonetDB and all extra modules and front ends) & are tested each night. During the weekend, the main (development) branches of all extra modules and front ends will additionally be tested together with the stable "Monet_4-3-14" branch. In case you have any questions, comments, problems about/with Monet_4-3-14, please feel free to contact me. Stefan Manegold (Stefan.Manegold(a)cwi.nl) -- | 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