Dear M5 developers, Currently, in the nightly testing, the cvs development trunk of the monet5 (aka. M5 or MonetDB/Five) code base is compiled and tested with the cvs development trunk ("Current") of MonetDB (v4.13) and SQL (v2.13), only. Since there is a tar-ball only alpha release of MonetDB/Five which is supposed to work with the 4.12/2.12 release of MonetDB/SQL, should the former also be tested with the latter, i.e., M5 alpha tar-ball with "Stable" M4/sql? I suppose, there is no release branch for monet5 (yet), nor has the code base for the M5 alpha tar-ball been tagged in CVS, right? 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 |
On 03-07-2006 11:46:35 +0200, Stefan Manegold wrote:
Since there is a tar-ball only alpha release of MonetDB/Five which is supposed to work with the 4.12/2.12 release of MonetDB/SQL, should the former also be tested with the latter, i.e., M5 alpha tar-ball with "Stable" M4/sql?
I think we should consider a few things: - is M5 ready for stable/dev separation? (I think not yet) - further releases should work against the stable versions (IMHO) - does M5 rely on "features" from M4 kernel, or not? (I don't know, currently not) Based on that I'd like to decide to either test against stable or current, as both will not really be of much added value. Maybe we should switch to stable now, and switch back to current when M5 relies on added features not in the stable branch.
I suppose, there is no release branch for monet5 (yet), nor has the code base for the M5 alpha tar-ball been tagged in CVS, right?
Of course it was tagged :) I even sent a mail about that to you. Unfortunately I just tagged with another naming scheme (not on purpose), so that's why you might not have found it.
participants (2)
-
Fabian Groffen
-
Stefan Manegold