Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <401AAFA1.10107@lokitech.com>
Date: Fri, 30 Jan 2004 14:25:21 -0500
From: Serge Knystautas <sergek@lokitech.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.6b) Gecko/20031205 Thunderbird/0.4
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [JIRA][Bugzilla][HttpClient] should I stay or should I go?
References: <400B945500071FB0@mssbzhb-int.msg.bluewin.ch>
In-Reply-To: <400B945500071FB0@mssbzhb-int.msg.bluewin.ch>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Oleg,

Sorry, I thought many of these points were addressed in the general 
discussion about commons and JIRA.  I will respond specifically to each 
of your questions below...

olegk@bluewin.ch wrote:
> * Do you actually encourage migration from Bugzilla to JIRA? Will it
> make the task of to administering and supporting projects'
> infrastructure (issue tracking in the first place) easier for you?

No, we will not encourage.

> * Can existing bug reports (including closed ones) be migrated to JIRA
> in their entirety, if at all? What kind of data would not be migrated
> automatically? Would existing user accounts be preserved?

Yes, existing bug reports can be transfered in their entirety.  There is 
a data migration process.  All accounts would also be preserved, 
although after the conversion, if you change your password in one place 
(JIRA or bugzilla), it won't change in the other.

> * We (HttpClient committers & contributors) have been in fact quite
> satisfied with Bugzilla so far. It has served us well. The only thing we
> have found constraining is the release management (versions, milestones,
> etc). 

Agreed, release management is really the kicker for why I wanted it for 
the James project and why I've been (slowly) getting JIRA running.

 > As an alternative to migration to JIRA would it be possible to
> promote HttpClient from a component of Jakarta-commons project to a full
> fledged top level project with its own set of versions and milestones?
> HttpClient has already got its own mailing list. HttpClient related
> content constitutes 20-30% Bugzilla entries for the Jakarta-commons
> project. I believe this might be the best option, as least as far as we
> are concerned. I am just not sure it is technically feasible.

I don't know who or if anybody maintains the bugzilla info.  I would 
send just this request to the infrastructure mailing list and hopefully 
someone can help.

-- 
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org