Add some BBDB tests
Hello, A few weeks ago I upgraded to BBDB git head and experienced some odd behaviours that I have to revert to my last working copy which is some months old. BBDB2 has some nice tests to ensure regression doesn't happen as often. Would that be a good idea for bbdb3? Leo -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Add some BBDB tests
On Sat Aug 11 2012 Leo wrote: A few weeks ago I upgraded to BBDB git head and experienced some odd behaviours that I have to revert to my last working copy which is some months old. Certainly it would be good if you could post here if anything appears to be a true regression. BBDB2 has some nice tests to ensure regression doesn't happen as often. Would that be a good idea for bbdb3? I guess in principle yes - yet setting up such a test suite and making sure that it does what it is supposed to do, is by itself a significant project, even if there was such a thing for BBDB2. I think it happens for good reasons that the GNU Emacs project (and most of its subprojects I am aware of) does not have such test suites. There is not enough manpower available to make such a thing work effectively. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)
On Mon, Jul 2, 2012 at 2:56 AM, Roland Winkler wink...@gnu.org wrote: I would like to capture this question and a summary of your answers as a FAQ on the updated project site on sourceforge. Thanks a lot, that will be helpful I have updated site (http://bbdb.sourceforge.net/) with a note pointing to Savannah. That done, I now feel it is best to just leave that site alone. Any FAQ etc. should reside on the Savannah site. Thoughts? -Karra -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)
On Fri Aug 10 2012 Sriram Karra wrote: I have updated site (http://bbdb.sourceforge.net/) with a note pointing to Savannah. That done, I now feel it is best to just leave that site alone. Any FAQ etc. should reside on the Savannah site. Thoughts? Thanks a lot for doing this. Two things: - My first name is Roland - I suggest to replace the 2nd paragraph by something like the following It is important to note that at the moment v3 can import a BBDB database from v2. Also, most concepts of the user interface have been preserved (plus many new concepts have been added to make BBDB yet more powerful). However, beyond this point v3 is not backwards compatible with v2. A database from v3 cannot be used with v2. Also, the names of many commands and user variables have been changed and v3 currently does not support Xemacs. Therefore, the rest of the page below will be kept around in state at least till support for Xemacs has been addressed somehow. You also mentioned backward compatibility that should / could be addressed. I do not know what this could mean more specifically. (I do not expect it will ever be feasible / useful to provide a compatiblity mode that allows a user of v2 to switch to v3 without worrying about anything.) Roland -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)
On Fri, Aug 10, 2012 at 11:15 PM, Roland Winkler wink...@gnu.org wrote: Thanks a lot for doing this. Two things: - My first name is Roland Ah, indeed :) - I suggest to replace the 2nd paragraph by something like the following I have rewritten along lines you have suggested and pushed it. Please take a look. You also mentioned backward compatibility that should / could be addressed. I do not know what this could mean more specifically. (I do not expect it will ever be feasible / useful to provide a compatiblity mode that allows a user of v2 to switch to v3 without worrying about anything.) Backwards compatibility for me would mean a few distinct things: 1. Will my old customizations work with the new code 2. If I use BBDB v3 and don't like it can I go back to v2 v3 fails the test on both counts. #1 might never get fixed given the direction we've headed. #2 can and should get fixed. I find it quite amusing in fact, the bbdb-migrate stuff has always had the hooks to downgrade to an earlier file format version - until now, i.e., when it is needed more than ever before really :) One of these days... -Karra -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)
On Sat Aug 11 2012 Sriram Karra wrote: I have rewritten along lines you have suggested and pushed it. Please take a look. Looks fine to me, thanks, Backwards compatibility for me would mean a few distinct things: 1. Will my old customizations work with the new code #1 might never get fixed given the direction we've headed. My intention has been to make the concepts more transparent. So yes, making old customizations work in an automated would be very difficult. 2. If I use BBDB v3 and don't like it can I go back to v2 #2 can and should get fixed. I find it quite amusing in fact, the bbdb-migrate stuff has always had the hooks to downgrade to an earlier file format version - until now, i.e., when it is needed more than ever before really :) One of these days... Well, the new format allows you to do things you could not do with the old format. So going back to v2 is only possible by throwing away the incompatible extensions in the format of v3. I do not consider this a satisfactory procedure. Of course, anyone switching from v2 to v3 should first make a copy of his or her old database. Then if things do not work out for whatever reason you can fully go back. Roland -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
