On Friday 20 August 2004 8:52, Thomas Bushnell BSG wrote: > In closing a bug report on bugzilla > (http://bugzilla.gnome.org/show_bug.cgi?id=150604), Derek Atkins asks > > me: > > Thomas: can you please attempt to verify bugs against cvs before you > > submit them? > > Really, probably, no. It's a bajillion times easier to report bugs > against the released version. I do not have the resources to keep a > running copy of the CVS head all the time, nor can I reasonably build > it every time I need to verify a bug.
But this makes it more difficult for developers to use the bug reports to fix problems! It diverts the effort back onto the developers, which is kinda unwelcome. I'm only helping out with one section, the main effort from the busier developers is already spread pretty thin. It means that instead of fixing the bugs, developers need to sift through old bugs - trying to find which ones still need to be fixed by trying to reproduce them in CVS HEAD themselves. Can't you use cron with a bash script? #!/bin/bash cd /path/to/top/CVS/local cvs update cd src make make install Do that once a week? It won't take many resources to do this whilst you sleep. The autogen bit only needs to be done once (see Derek's reply to my previous message when I asked the same thing) https://lists.gnucash.org/pipermail/gnucash-devel/2004-August/011931.html > Heck, this is one of the reasons for having regular releases. ;) But, right now, there's a lot of work on the gnome2 branch that is still a while from release. Until that's ready, the developer effort is split and therefore releases will become less regular. > I'm convincable, but it seems reasonable to me to verify bugs against > the release, before reporting them, rather than needing to deal with > the bleeding edge. Yet the CVS is where the bug will be fixed and where the next release will be created. > I am willing to make an effort in the future to > see if they are fixed by source perusal as well if that is desired. If the bug report has a decent amount of information such that you can reproduce it in a release copy, reproducing it in a CVS build will be just as simple. Far easier than grinding through the source trying to find the exact function call. After all, the bug report will be in terms of which menu item to click, not which source file is responsible for the active code. -- Neil Williams ============= http://www.codehelp.co.uk/ http://www.dclug.org.uk/ http://www.isbn.org.uk/ http://sourceforge.net/projects/isbnsearch/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3
pgps34i8yYlbH.pgp
Description: signature
_______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
