Hi, Often when we find a bug in some code we use, we work around it in amsn code, or have a local patches copy of the other project. (2 latest example are commits 8758 (DEMANDS_ATTENTION) and 8759 (snit <> tcl 8.5a6 ). It is absolutely very good that we do this, and we should continue doing so. However, these fixes are not necessary (anymore) when they are fixed by upstream projects.
So I thought it might be good to have a page in the wiki for all workarounds we do, and the corresponding upstream bugreport. This way, if by any chance there is a regression because of a workaround, instead of working around the workaround we could check the upstream status, and if it is fixed there we could revert the workaround (if it would be easy for users to update the upstream code), or at least we know a bit what's going on. In the longer term this will lead to less workarounds, and less bugs in upstream software. What do you guys think? Sander ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
