From 63d8aa7cb12283b1fc6ec54289cadd3a5ec2d4be Mon Sep 17 00:00:00 2001 From: mh Date: Sun, 8 Dec 2002 04:59:51 +0000 Subject: [PATCH] know bugs and reporting new ones --- doc/KNOWN_BUGS | 18 ++++++++++++++++++ doc/REPORTING_BUGS | 41 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 59 insertions(+) create mode 100755 doc/KNOWN_BUGS create mode 100755 doc/REPORTING_BUGS diff --git a/doc/KNOWN_BUGS b/doc/KNOWN_BUGS new file mode 100755 index 00000000..4a43fef9 --- /dev/null +++ b/doc/KNOWN_BUGS @@ -0,0 +1,18 @@ +last changed: $Date: 2002/12/08 04:59:51 $ 2002 mir-codes +------------------------------------------------------------------- + +In all versions +=============== + +* the JAI library used for creating thumnails of images will often make the + thumbnail for a GIF or PNG image look like it has some television set snow in + it. The workaround would be to upload Jpeg images if you can. We are looking + into replacing JAI with another library. + +* when deleting an item, be it an article or an uploaded media file, the action + will remove the data/meta-data from the DB and prevent it from show up in + lists, but it will not delete the file from the filesystem. hopefully this + will be fixed before 1.1.0 is released and in 1.0.1. (FIXME: is this still a + problem in the HEAD branch?) + +* some others that I'm forgetting now. diff --git a/doc/REPORTING_BUGS b/doc/REPORTING_BUGS new file mode 100755 index 00000000..179e1778 --- /dev/null +++ b/doc/REPORTING_BUGS @@ -0,0 +1,41 @@ +last changed: $Date: 2002/12/08 04:59:51 $. 2002 mir-coders +-------------------------------------------------------------------------- + +BUG REPORTS + +Please read this file before sending in a bug report or patch. + +Where to send +============= +Send comments, bug reports, patches, etc. to mir-coders@lists.indymedia.org + + +What to send +============ +Please specify the relevant versions of the software that you are running Mir +under. i.e JVM name and version (IBM, Sun,..), what compiler was used +(javac or jikes), tomcat version. + +Of course, you should always specify what version of Mir you are running. If you +are running a version check'out of CVS, please specify when you checked it out +and from which branch (e.g MIR_1_0, HEAD..). Also if you can specify the +versions of relevant files using "cvs status". + +If you received an Exception while running Mir, please mail in the "Oops" you +got (if you got one) and try to find and error in one of the Mir/log/* files. +Also, a stack trace can usually be found in one of the tomcat log files. For +example, in tomcat4 you can look at the .../logs/catalina.out file or the +.../logs/localhost_log.yyyy-mm-dd.txt, where the date is of the last time +tomcat was started. Under the Debian package installation, the tomcat logs can +be found under /var/log/tomcat... It is probably similar for other +distributions. If you are using the tarball from jakarta.apache.org, the logs +dir. is directly in the root of the tomcat tree. + +Patches +======= + +Please send in patches that are a diff between an unmodified tree and your tree +with the changes: + +diff -Nur standard-mir-dir your-mir-dir + -- 2.11.0