Feature Requests item #2184885, was opened at 2008-10-21 18:40 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482471&aid=2184885&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: MonetDB - general Group: None Status: Open Priority: 5 Private: No Submitted By: Stefan de Konink (skinkie) Assigned to: Nobody/Anonymous (nobody) Summary: Add CVS version information too all versions Initial Comment: I think it would be a great improvement if the version string (in svn it is usually named the rXXXX) plus compilation date after the actual named version. In this case when bugs are reported it is clear to see if the reported is using the latest CVS version; the assignee knows what version of the code is running. There are reasons to say that a user should always upgrade to cvs head, for me this would mean that after every problem I find I need to spend 30 minutes on upgrading the code to find it out. Might be better to just report the issue, and get it marked as fixed, if the problem is already fixed. This will probably also make a difference for users (like me) that are compiling new code and expect a new version. If they see that the actual revision/date the code was changed for a specific subpart has not been changed between releases this could point out that something went wrong with the compilation and the user might be still running an older version. ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2008-10-21 23:31 Message: In contrast to SVN, CVS has not global revision number, but each file has its own revision number; and since CVS allows updates of individual files to arbitrary revisions, the only "water proof" and hence "useful" solution would be to add and list the revision number of all (code) files --- that is a lot in MonetDB, and hence hardly feasible ... Maybe, we could consider creating a checksum of all code files or so? Apart from that, users are welcome to report bugs for whatever version they are using, preferably the latest "Stable" release. In that case, the can simply say "using latest Stable release version X.Y.Z" or "CVS checkout/update from latest Stable release branches on <date>, <time>, preferably adding the output of `mserver5 --version` and `mserver5 --dbinit='include sql;'` or `Mserver --dbinit='module(pathfinder);'`. Provided the bug report comes with sufficient instructions to (easily) reproduce the steps that triggered the bug with the user, the developers will be able to check whether it does or does not work with both the latest CVS version of the latest release branches (or the development trunk) and only once the developers have either confirmed that the problem has already been fixed, or once it is fixed, the user needs to upgrade to the latest CVS version (preferably from the latest release branches, where the problem has been fixed). For most users, using the "Current" development trunk is only "necessary", if they indeed require the latest (not necessarily stable) "cutting-edge" features. ---------------------------------------------------------------------- Comment By: Sjoerd Mullender (sjoerd) Date: 2008-10-21 23:16 Message: Adding the CVS version information is not feasible: every source file has its own CVS version number and there are hundreds of source files. In CVS there is no such thing as a global version. ---------------------------------------------------------------------- Comment By: Stefan de Konink (skinkie) Date: 2008-10-21 22:39 Message: MonetDB server v5.7.0 (32-bit), based on kernel v1.25.0 (32-bit oids) Copyright (c) 1993-July 2008 CWI Copyright (c) August 2008- MonetDB B.V., all rights reserved Visit http://monetdb.cwi.nl/ for further information Configured for prefix: /opt/monetdb Libraries: libpcre: 7.8 2008-09-05 (compiled with 7.8) openssl: OpenSSL 0.9.8i 15 Sep 2008 (compiled with OpenSSL 0.9.8i 15 Sep 2008) Compiled by: [EMAIL PROTECTED] Compilation: gcc -Wall -Wextra -std=c99 -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 Linking : /usr/i686-pc-linux-gnu/bin/ld This would still not allow you to say what CVS I'm running night? What I would suggest is: MonetDB server v5.7.0-CVS XXXXXX (32-bit), based on kernel v1.25.0-CVS XXXXXX (32-bit oids) MonetDB/SQL module v2.25.0-CVS XXXXXXX loaded ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2008-10-21 22:29 Message: Posting the output of `mserver5 --version` comes sort of close, as it gives us answers to some questions regarding your setup. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482471&aid=2184885&group_id=56967 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
