You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Serge Knystautas <se...@lokitech.com> on 2003/01/18 16:11:40 UTC
JIRA for James
I brought this up a while ago, but since the folks that run nagoya
didn't seem to interested, I didn't push it further.
However, I've just come to know that Forrest uses JIRA, and Peter Donald
is planning to move Avalon to JIRA (this was 2 months ago, so may have
changed his mind since).
We're in the process of migrating all our commercial development from
Bugzilla to JIRA because it's just a much better issue tracking system.
Better interface, faster, more flexibility, release management... And
it's free for open source projects.
Anyway, since other Apache projects seem to be adopting it, I think it's
worth considering. I think anyone who tries JIRA will have a hard time
arguing against it. :)
--
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JIRA for James
Posted by Harmeet Bedi <ha...@kodemuse.com>.
----- Original Message -----
From: "Serge Knystautas" <se...@lokitech.com>
> Nicola Ken Barozzi wrote:
> > Not really, I was addressing your comment about IssueZilla that
> > Collabnet uses (Tigris is of Collabnet).
>
> Yeah, that was Harmeet's comment actually.
I was saying OpenOffice uses it and Collabnet promotes it. Don't know more
about it though. I was concerned that we may take a path that is
incompatible in the long term.
For instance Perforce is the best Source Control system I have used and it
has an open source license, transactional commits, web interface,
notifications, ftp etc. etc. but Apache direction seems to be CVS and then
Subversion. It would be painful for folks to learn two or more Source
control systems esp. as a lot of developers may work on multiple projects. I
have the same concern for Bugzilla and the next bug tracking system.
Harmeet
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JIRA for James
Posted by Serge Knystautas <se...@lokitech.com>.
Nicola Ken Barozzi wrote:
> Not really, I was addressing your comment about IssueZilla that
> Collabnet uses (Tigris is of Collabnet).
Yeah, that was Harmeet's comment actually.
> As for Scarab, it will most probably be usde because Pier, the Bugzilla
> guy, is more than fed up with admininstring Bugzilla, and will change as
> soon as he can to a better system. AFAIK there is no other OS bug
> tracking system other than Scarab...
I can definitely sympathize with Pier. When I mentioned JIRA to him
privately, he sounded pretty stressed in general from dealing with this. :)
>> OpenSymphony is a smaller but similar high-quality Java open source
>> project
>> depot (similar to Jakarta), and I think the affiliated business
>> (Atlassian)
>> has produced something a lot better than Scarab in JIRA.
>
>
> It's not OS, and some have espressed that they would feel more than
> uneasy to use it for all Apache.
Yeah, there's a lesson here in how to make a profit on top of the open
source market... CollabNet is doing something very similar to Atlassian
in that CollabNet has proprietary extensions that they will use to have
a sellable version of Scarab. Meanwhile, Atlassian didn't open source
the core but justs licenses it for open source use for free... just
interesting to see how the different strategies are playing out.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JIRA for James
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Serge Knystautas wrote:
> ----- Original Message -----
> From: "Nicola Ken Barozzi" <ni...@apache.org>
>
>
>>Collabnet will move to Scarab once it's released, and I'm confident that
>>Apache will encourage users to move to Scarab too.
>>
>>As for Avalon, we are sticking with Bugzilla for now.
>
>
> Yeah, I'm somewhat disappointed CollabNet has such influence over the Apache
> infrastructure. Don't get me wrong, I'm incredibly appreciative of their
> huge and long-term contributions. Just that we seem to be heading towards
> Scarab, based largely because CollabNet has sponsored that project.
Not really, I was addressing your comment about IssueZilla that
Collabnet uses (Tigris is of Collabnet).
As for Scarab, it will most probably be usde because Pier, the Bugzilla
guy, is more than fed up with admininstring Bugzilla, and will change as
soon as he can to a better system. AFAIK there is no other OS bug
tracking system other than Scarab...
> OpenSymphony is a smaller but similar high-quality Java open source project
> depot (similar to Jakarta), and I think the affiliated business (Atlassian)
> has produced something a lot better than Scarab in JIRA.
It's not OS, and some have espressed that they would feel more than
uneasy to use it for all Apache.
> Anyway, had garnered some hope by seeing that Forrest and (maybe, but guess
> not) Avalon would be using it. If the future is already set, then no
> worries.
Personally, I prefer Bugzilla both to JIRA and Scarab. Why? I'm used to
it, and it simply works for me for what I need. (Thanks Pier) ;-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JIRA for James
Posted by Serge Knystautas <se...@lokitech.com>.
----- Original Message -----
From: "Nicola Ken Barozzi" <ni...@apache.org>
> Collabnet will move to Scarab once it's released, and I'm confident that
> Apache will encourage users to move to Scarab too.
>
> As for Avalon, we are sticking with Bugzilla for now.
Yeah, I'm somewhat disappointed CollabNet has such influence over the Apache
infrastructure. Don't get me wrong, I'm incredibly appreciative of their
huge and long-term contributions. Just that we seem to be heading towards
Scarab, based largely because CollabNet has sponsored that project.
OpenSymphony is a smaller but similar high-quality Java open source project
depot (similar to Jakarta), and I think the affiliated business (Atlassian)
has produced something a lot better than Scarab in JIRA.
Anyway, had garnered some hope by seeing that Forrest and (maybe, but guess
not) Avalon would be using it. If the future is already set, then no
worries.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JIRA for James
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Harmeet Bedi wrote:
> I would be curious what ASF thinks about IssueZilla. It seems to be the next
> iterations of Buzilla maybe like CVS->Subversion. I don't know a lot about
> it but OpenOffice uses it and Collabnet promotes it.
> There is some information about it here.
> http://eyebrowse.tigris.org/project/www/docs/ProjectIssues.html#aboutIZ
>
> The reason why I raise issue zilla is that it would be bad if one does
> Bugzilla->Jira and then to another system after that. Would be good to see
> if IssueZilla can address some of the concerns
>
>> Better interface, faster, more flexibility, release management...
>
> and be better long term direction.
Collabnet will move to Scarab once it's released, and I'm confident that
Apache will encourage users to move to Scarab too.
As for Avalon, we are sticking with Bugzilla for now.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JIRA for James
Posted by Harmeet Bedi <ha...@kodemuse.com>.
I would be curious what ASF thinks about IssueZilla. It seems to be the next
iterations of Buzilla maybe like CVS->Subversion. I don't know a lot about
it but OpenOffice uses it and Collabnet promotes it.
There is some information about it here.
http://eyebrowse.tigris.org/project/www/docs/ProjectIssues.html#aboutIZ
The reason why I raise issue zilla is that it would be bad if one does
Bugzilla->Jira and then to another system after that. Would be good to see
if IssueZilla can address some of the concerns
>
> Better interface, faster, more flexibility, release management...
and be better long term direction.
Harmeet
----- Original Message -----
From: "Serge Knystautas" <se...@lokitech.com>
To: <ja...@jakarta.apache.org>
Sent: Saturday, January 18, 2003 7:11 AM
Subject: JIRA for James
> I brought this up a while ago, but since the folks that run nagoya
> didn't seem to interested, I didn't push it further.
>
> However, I've just come to know that Forrest uses JIRA, and Peter Donald
> is planning to move Avalon to JIRA (this was 2 months ago, so may have
> changed his mind since).
>
> We're in the process of migrating all our commercial development from
> Bugzilla to JIRA because it's just a much better issue tracking system.
> Better interface, faster, more flexibility, release management... And
> it's free for open source projects.
>
> Anyway, since other Apache projects seem to be adopting it, I think it's
> worth considering. I think anyone who tries JIRA will have a hard time
> arguing against it. :)
>
> --
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>