Since this is a feature release, this can still be done. We can think about setting the minimum required versions later. I would need to add that to my scripts that I use to prepare a release, but that is not a big deal.

Stefan Manegold wrote:

Sjoerd, fellow developers,

I just realize the following:

(at least) due to my recent changes, (at least) MonetDB4 & MonetDB5 in the Aug2009 release branch (most probably) do no longer compile with an earlier version of MonetDB common (GDK), mainly because I added (for convenience) the assert_shift_width() C macro to gdk.mx/gdk.h .

It could well be, that binary build of the latest versions of MonetDB4 & MonetDB5 still work with binary builds of earlier versions of MonetDB common (GDK); at least I'm not aware of any interface changes.

Hence, unless we remove the assert_shift_width() C macro, again (and implement its functionlity differently), we'd need to make the upcoming MonetDB-4.32.0 and MonetDB-5.14.0 requiring MonetDB-1.32.0. However, this also changes the dependencies for the binaries.

Well, given our regular release cycle, and Windows installers and super source balls that contain "everything", anyway, I don't expect too many users that would like to upgrade only M4 or M5 or sql, while keeping the "old" GDK ...

Hence, to be on the save side, I'd propose to update all dependecies in the Aug2009 branch to require part from that very branch (and possibly introduce this as a standard procedure, unless/until we indeed do partial releases).

Any thoughs, comments, objections?

Thanks!

Stefan