Folks,
As a result of the discussion my assumption is that we want to go ahead
with migration from Bugzilla to JIRA. If you have any objections or
concerns it is the right time to voice them. I am going to update the
change request http://issues.apache.org/jira/browse/INFRA-74 shortly
stating out
Folks
Due to the recent upgrade of HttpClient to a full project in Bugzilla
JIRA no longer has a definitive edge over Bugzilla. Nonetheless, JIRA
still a newer and more flexible system which can potentially make our
life and that of our users simpler.
Hi Oleg,
could we synchronize the switch with the 4.0 implementation?
In other words, continue with Bugzilla for 2.0 and 3.0, but once
work gets started on 4.0, where the API changes and the package
names probably change, then the bug tracking system changes
as well?
cheers,
Roland
Hi Roland
I agree this makes sense. I am not sure, though, whether we can
reasonably expect things to happen in one 'Big Bang': mailing lists, new
CVS repository, web site, JIRA migration and so on. Most likely not.
Besides, unless we start getting MASSIVELY more feedback on 3.0, I am
not sure
Between Bugzilla and JIRA, JIRA is my preference.
-D
On Mon, 11 Oct 2004 17:34:12 +0200, Oleg Kalnichevski
[EMAIL PROTECTED] wrote:
Hi Roland
I agree this makes sense. I am not sure, though, whether we can
reasonably expect things to happen in one 'Big Bang': mailing lists, new
CVS
I agree this makes sense. I am not sure, though, whether we can
reasonably expect things to happen in one 'Big Bang': mailing lists,
new
CVS repository, web site, JIRA migration and so on. Most likely not.
Another question is if we want to switch to Subversion when we go to
4.0. It sounds like
