hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Becke <be...@u.washington.edu>
Subject Re: [HttpClient][Bugzilla] should I stay or should I go?
Date Fri, 30 Jan 2004 17:07:18 GMT
I see nothing wrong with your original email.  Perhaps an email to 
commons-dev would be helpful.

Mike

On Jan 30, 2004, at 11:57 AM, Kalnichevski, Oleg wrote:

> Folks,
> Did I say something glaringly stupid in my message below? It's been a 
> week since I sent this request. I have not received a single response 
> so far. Any idea what may be wrong? Or are our infrastructure folks 
> simply too overwhelmed these days sorting out MyDoom mess? Shall I 
> forward the original message to commons-dev list?
>
> Oleg
>
> -----Original Message-----
> From: Oleg Kalnichevski [mailto:olegk@apache.org]
> Sent: Thursday, January 22, 2004 21:28
> To: infrastructure@apache.org; jira@apache.org
> Cc: Jakarta Commons HttpClient mailing list
> Subject: [HttpClient][Bugzilla] should I stay or should I go?
>
>
> Good day,
>
> Following the proposal to migrate Jakarta Commons projects from 
> Bugzilla
> to JIRA posted to the Jakarta commons-dev list, we would like to have a
> few points clarified, before the final decision can be made whether
> Jakarta Commons HttpClient project stays with Bugzilla or migrates
> (kindly requests to be migrated) to JIRA.
>
> * 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?
>
> * 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?
>
> * 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). 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.
>
> Cheers,
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: 
> commons-httpclient-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: 
> commons-httpclient-dev-help@jakarta.apache.org
>


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


Mime
View raw message