Process for checking in files and resolving bugs

["David M. Karr" <dm...@earthlink.net>]

Outside of adding a reasonable checkin comment, is there some other process or
information that is needed when I'm checking in files?

I noticed that when I try to use the internal "cvs" interface in XEmacs, I'm
unable to complete the commit process (gnuclient's connection gets "reset by
peer"), although this might be some problem with XEmacs and/or gnuserv.  I have
no problem checking files out with this interface.  When I do try to submit
using this interface, the buffer gets filled in with some comments, like saying
that I should fill in a "PR" number, which I would guess is the bugzilla
problem report number.  When I do this submit in WinCVS (as I can't get it done
with XEmacs), the checkin comments buffer doesn't show that information.  I'm
not certain exactly what initializes that buffer.

With respect to any bug number that I'm submitting code against, what is a
reasonable process for verifying the bug is "fixed" so I can resolve it?  I can
easily test it in my distribution, but do I have to install and test it in the
next nightly build, or what?

-- 
===================================================================
David M. Karr          ; Java/J2EE/XML/Unix/C++
dmkarr@earthlink.net


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>