issuezilla is the ancient version of bugzilla that I mentioned.
Collabnet runs the infrastructure and uses issuezilla for issue tracking.
projects like openjdk.java.net are however not run by collabnet and use
different infrastructure. That's why I said xyzzy.dev.java.net since
collabnet provides the infrastructure for everything under .dev.java.net
- David Herron
Wim Verreycken wrote:
> Hi everyone,
>
> Thanks everyone for the replies received allready. But I'm left with a bit
> more confusion now. These are the answers received to this moment (quoting):
>
> David Herron :
> “xyzzy.dev.java.net projects use an ancient version of bugzilla.”
>
> Kedar Mhaswade :
> "It's the issuezilla."
>
> Pat Patterson :
> "java.net is powered by CollabNet - http://www.collab.net/"
>
> Now while it possible different projects on java.net use different issue
> tracking backends, I would find it a bit strange. It would seem more logical
> to me the issue tracking on java.net was consolidated by a single software.
> So I'm still not sure. The question remains :)
>
> Wim
> -----Original Message-----
> From: Wim Verreycken [mailto:wim_at_pizzastop.be]
> Sent: donderdag 18 december 2008 17:58
> To: quality_at_glassfish.dev.java.net
> Subject: open source issue tracking / change+release management
>
> Hi everyone,
>
> I'd like to use the issue tracking software used by java.net for issue
> tracking/ release/change management for internal use by one of my clients.
> If it includes workflow management it would be even better.
>
> I know there's plenty of solutions around, but I'd like obtain somewhat the
> same result. So it’s probably best to start off with the same software
> package.
>
> Does anyone have any info on this?
>
> Lots of thanks in advance.
>
> Wim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>
>