> From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Ulrich Mayring > > Berin Loritsch wrote: > > > > The bottom line is that we are willing to help users of the > > release. > > Maybe I'm in the wrong projects, but wherever (here too!!) I asked a > question about cvs code people helped me. There is no such thing as > formal support in OpenSource projects. But very rarely will the > developers not be interested in user questions - but in my experience > they don't make a distinction between releases and cvs code.
I'm not saying we treat you like dogmeat if you are running CVS code. All I am saying is that if we have users that are forced to work with only released code, then we have to be willing to help them make the release work. If that means that with XYZ release, you can't upgrade your jars with PDQ library yet, we need to let them know those constraints. IOW, if I am only allowed to use released code by my boss, or by the practicalities of not being able to keep up with CVS changes in another open source project, then instead of saying "if you go with current CVS you can XYZ PDQ as well as fix the problem you are having". > Maybe you mean: when something's broken in a release all > developers put > everything else aside and work on that bug? In contrast, when > something > in cvs is broken, it's not a first priority? If a user supplies a bug report for released code, we should be able to incorporate the fix right away (provided the user isn't too vague). If a user supplies a bug report for CVS code, you have to make the determination whether the code still exists (#1), and if it is "transitional" (#2). If the code no longer exists, but the bug still does, the fix supplied in the bug report won't work. OTH if the code no longer exists, there is a good chance that the bug is gone as well. If the code exists, but was introduced as a place holder until more robust code could replace it, you might not want to expend the energy on the fix. In either case, if the bug report is for existing code, we need to fix it ASAP. Bugs are bad. Not only should we fix the bug, but we should add a testcase to make sure it doesn't creep back in. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
