Folks,
I just filed a request for Bugzilla upgrade.
http://nagoya.apache.org/jira/browse/INFRA-73
Let's see if we have more luck taking that route.
I have an impression that Jira is to eventually supersede Bugzilla. All
the new project who have no or little Bugzilla legacy tend to opt for
This looks like a good alternative to get some attention from
infrastructure.
Moving to Jira seems more and more likely to me.
Mike
On May 2, 2004, at 3:07 PM, Oleg Kalnichevski wrote:
Folks,
I just filed a request for Bugzilla upgrade.
http://nagoya.apache.org/jira/browse/INFRA-73
Let's see
Quote from Serge Knystautas:
- Bugzilla is what most projects still use. It is running an old
version that could benefit from an upgrade... someone recently
volunteered to do the upgrade, but I don't know if this was done. There
is no one who proactively maintains it, but people on
[EMAIL
Folks,
It's been a week, there's no response, and I suspect there'll be none.
What else shall I do? Threaten them with a preventive nuclear strike?
I have an impression that Bugzilla is simply no longer supported, which
poses an important question why should we continue using it.
Shall I try
I forget what we decided when this was last discussed, but I am all for
moving to Jira.
If we do stick with Bugzilla, I don't think we should bother
[EMAIL PROTECTED] about this one. This is something that the
infrastructure list is for. Let's give them a little more time. Perhaps
a quick
If my memory does not fail me, the general sentiment was to stick to
Bugzilla if HttpClient gets to be a top level project in the Bugzilla
database (in order for us to be able to define own releases and
milestones independently from Commons).
That sounds about right.
IMO Bugzilla has been
Good ${time of the day},
HttpClient has recently been promoted to the Jakarta subproject level.
As a first step in the transition process we would like to have a new
project created in the Bugzilla database and have Commons HttpClient
related entries migrated from Commons project to the new one
