[Prism54-users] Bugs and patching procedures

[Luis R. Rodriguez]

I've added Bugs and patches procedures to the README. Thought I'd throw
them out here to keep you updated.

---

Bug reports
-----------

Bugs? What? No way! Yeah, just take into consideration that we haven't yet
released a stable driver or even a "testing" one. The driver should be
*usable* but since all the releases are snapshots we can't gaurantee
anything.

Honestly, if you happen to detect some (software) bug in the driver
please take the time and act according to the following recommended
procedures:

1. Might want to quickly check on IRC see if someone knows anything about
the issue first. Check with #prism54 on irc.freenode.net. Check then our
Bugziilla to see if you find the bug already reported.

2. Next, try the mailing lists. If you're *sure* it's a bug then send
an e-mail out to prism54-devel@prism54.org. If you're not sure if it is a
bug
and would like insight on the issue send an e-mail out to
prism54-users@prism54.org.

3. If you get confirmation that it is a bug you can
then procceed to report it on our Bugzilla. Our bugzilla database
can be reached at http://prism54.org/bugzilla/

Note: our bugzilla should be sending out e-mails to
prism54-devel@prism54.org but I think it stopped... If we get it working
again then if you 100% sure what you found is a bug then you can just
submit the bug to Bugzilla.

Submitting Patches
-------------------

If you have a patch just send it to prism54-devel@prism54.org. But first:

1. Check first through the prism54-devel@prism54.org mailing
list to see if someone is already working on it; or check on the
#prism54-devel IRC channel too.

2. Make sure your patch is unified,
diff -Naur prism54-cvsxxxx-new prism54-cvsxxxx > description_fix.diff
works well.

2. Name the bugs, if any, that your patch fixes from Bugzilla. Close them
if your patches was commited (or we can do it for you).

--
	Luis