AW: JIRA or Bugzilla?

2005-03-10 Thread Jan . Materne
Asking infrastructure for their preferences would be good - maybe they want
to
kill bugzilla as cvs :-)

And IMO we could wait for starting the new project and bugtracking until
they´ve
solved the problems ... if it needs only a few weeks.

But we should have a the same infrastructure for the whole ant project
- same scm system for ant core and ant libs (svn)
- same bugtracking for ant core and ant libs (whatever)

Personally I´d prefer Bugzilla, because I am familiar with that. Jira would
be 
complete new to me. Nearly the same as svn. But that´s a solvable problem.

Jan

 -Ursprüngliche Nachricht-
 Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
 Gesendet am: Donnerstag, 10. März 2005 11:24
 An: [EMAIL PROTECTED]
 Betreff: JIRA or Bugzilla?
 
 Hi,
 
 lurking on the infrastructure list shows that we do have stability
 problems with JIRA and Tomcat on issues.apache.org, so right now I'd
 prefer to stick with Bugzilla.
 
 Even without that I'd suggest we ask the infrastructure team what
 they'd prefer us to use before we make any decision.
 
 Comments?
 
 Stefan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


Re: AW: JIRA or Bugzilla?

2005-03-10 Thread Steve Loughran
[EMAIL PROTECTED] wrote:
Asking infrastructure for their preferences would be good - maybe they want
to
kill bugzilla as cvs :-)
And IMO we could wait for starting the new project and bugtracking until
they´ve
solved the problems ... if it needs only a few weeks.
But we should have a the same infrastructure for the whole ant project
- same scm system for ant core and ant libs (svn)
- same bugtracking for ant core and ant libs (whatever)
Personally I´d prefer Bugzilla, because I am familiar with that. Jira would
be 
complete new to me. Nearly the same as svn. But that´s a solvable problem.

Jan

Axis is using Jira; I'm not 100% happy with the text of the messages it 
sends out, but it seems reliable.

Go to http://issues.apache.org/jira/secure/Dashboard.jspa
and create your own account to scope it out.
What is nice is that it integrates w/ SCM if you set up your keywords 
right and include bug#s in check ins, then you can search for all 
patches related to a defect. There is good meta-level reporting, the 
thing managers like

we use it internally with subversion; I think we'd like to do that for 
the OSS core we work on, but the sourceforge infrastructure isnt ready 
for either, so we'd have to host ourselves (not that hard, we have a 
8mbit optical link to the uk superjanet network so that CERN can run LHC 
simulations on the ia64 rack :), its just the extra operational effort.

Regarding SVN, people like it for its transacted approach; you get 
atomic operations. I miss the IDEA integration, but here the eclipse 
plugin is good, and I'm sure that IDEA will catch up. Its less important 
with the ant codebase as I tend to do fewer major refactorings (like 
moving entire packages). It can create support calls related to proxies

IMO a move to Jira is less traumatic than an SVN migration. One changes 
the web ui for bugs, the other transforms how your code is accessible. 
What is important with a JIRA migration is that the bugzilla repository 
gets locked off the moment it happens. All old urls should still 
resolve, but nobody should be allowed to edit existing bugs in bugzilla; 
they should all be moved to jira.

-steve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]