Hi, We have a 2.2b1 release slated for next Monday so I started looking at Bugzilla again and I realize why I never look at it. It's a horrible piece of software and is needlessly complicated.
For the release I would like to have a more comprehensible issue tracking mechanism and patch tracking mechanism. I'm not sure what state Scarab is in but if it can be used for these two things then that would be great and that's my first choice. If someone volunteers, by Wednesday, to setup a Scarab installation and commits to maintaining it then I say we go for Scarab. If there are no volunteers then I want to setup a sourceforge account to track bugs and patches because I refuse to use Bugzilla as it's a piece of crap and I would like something to help us keep track of patches. The SF interface isn't great but it has a very simple interface and I find it at least usable.I would prefer not to use SF but I'm not going to get around to setting up permanent Scarab installation this week. Maybe we can start with SF and move to Scarab as time permits I know that everyone is busy. Thoughts and input welcome. The docs and site management will be taken care of by maven but the issues and patches need a better mechanism. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
