Subject: Grouper Developers Forum
- From: "blair christensen." <>
- To: grouper-dev <>
- Subject: Grouper issue tracking
- Date: Mon, 7 Aug 2006 11:52:20 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=bODgdhNUwtkTR6nNld3NmLA0bO0pGLja0FuZaASrCcZhvGgtXU1jt2bElZDx680NjZyiqI4oX4t7ouqiuYEz7wwWwzdIL7zNNXLlEWvxBDVbo9uVQYVWzHErwerTTDdFC6SMKtG3CP5jtni9g8erxTC9/e2FTiLiNJdEW3TOAQ4=
For the past week I've been experimenting with using Google Code as a
replacement issue tracker for Grouper. I've set up a test
[i2mi-grouper project] which I have been using.
As anyone who has looked at Grouper's Bugzilla instance lately can
tell I haven't been paying much (well, any) attention to it. Far too
often Bugzilla felt like more of a hindrance while working through
reported issues, its searching and categorizing capabilities and
restrictions always frustrated me, and in most cases I would spend
more time dealing with Bugzilla than with the actual reported issues.
Now, Google Code is far from perfect but even with its current flaws
it has been more enjoyable to work with than Bugzilla. Of course, if
Google fixes the issues I've reported it will be a lot more usable.
I think it is "good enough" at this point but I would be curious to
know how others felt about it - and switching to it.
- Grouper issue tracking, blair christensen., 08/07/2006
Archive powered by MHonArc 2.6.16.