Re: [Bugzilla] vs [JIRA] revisited
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 intention to proceed with the migration if no one speaks out. Oleg On Mon, 2004-10-11 at 16:12, Oleg Kalnichevski wrote: 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. http://nagoya.apache.org/jira/browse/INFRA-74 The only fundamental gripe with JIRA that some folks have is that it is not open-source. I do not think we should try to be holier than the Pope himself, since too many projects have already defected to JIRA Religious reasons aside, I also foresee technical difficulties too. Currently (at least with Bugzilla 2.14.2) there appears no way to make a project completely read-only. Submission of new reports can be disabled, but one can still modify the existing bug reports. There is a few options: (1) Ask folks to resubmit their comments in JIRA when important / ignore modifications made in Bugzilla when unimportant. (2) Tweak Bugzilla a little to prevent mutation of existing reports. Note, supposedly Apache Bugzilla is already a fork. So, the real trouble here is to convince the Infrastructure folks to apply a patch, and more importantly reapply it every time Bugzilla is upgraded. Now, the REAL REAL trouble is that it almost took a full scale nuclear conflict between the Evil Russian Empire (me) and the Freedom Alliance (the Infrastructure team) to implement what turned out to be a fairly minor change to get HttpClient promoted to a project status. From now on, I am deeply skeptical about everything that has to do with Bugzilla maintenance. Besides, I may not survive yet another squabble with Noel. (3) Wait until other Jakarta Commons project migrate first. Long may be the wait, though So, what's the popular opinion on that? Non-committers are highly encouraged to voice their opinion too Evil Comrade Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] HttpClient is now a separate project in [Bugzilla] issue tracking system
On Tue, 2004-10-12 at 03:42, Michael Becke wrote: Hi Oleg, How do we go about adding versions, target milestones, etc? Mike Mike, We still will have to ask the Infrastructure. The good news is creating new versions and milestones in Bugzilla takes no special trickery, so it _should_ be relatively easy. Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] HttpClient is now a separate project in [Bugzilla] issue tracking system
We should be able to arrange for someone to have bugzilla admin privileges so they can do it. At the very least someone from the Jakarta PMC should be able to do it. Adrian. On 12/10/2004, at 7:36 PM, Oleg Kalnichevski wrote: On Tue, 2004-10-12 at 03:42, Michael Becke wrote: Hi Oleg, How do we go about adding versions, target milestones, etc? Mike Mike, We still will have to ask the Infrastructure. The good news is creating new versions and milestones in Bugzilla takes no special trickery, so it _should_ be relatively easy. Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Intencha tomorrow's technology today Ph: 3420 4584 0422236329 35 Prenzler St Upper Mount Gravatt 4122 Australia QLD www.intencha.com PGP.sig Description: This is a digitally signed message part
Re: [ANNOUNCE] HttpClient is now a separate project in [Bugzilla] issue tracking system
Adrian, That would be quite handy. We have over a dozen milestones (pre 2.0.3 and 3.0b1) that are no longer relevant and should clean up at some point. Do you know how we are supposed to go about asking for Bugzilla privileges? We do not need a full blown admin privileges. In Bugzilla terms we need 'edit components' permission Oleg On Tue, 2004-10-12 at 12:02, Adrian Sutton wrote: We should be able to arrange for someone to have bugzilla admin privileges so they can do it. At the very least someone from the Jakarta PMC should be able to do it. Adrian. On 12/10/2004, at 7:36 PM, Oleg Kalnichevski wrote: On Tue, 2004-10-12 at 03:42, Michael Becke wrote: Hi Oleg, How do we go about adding versions, target milestones, etc? Mike Mike, We still will have to ask the Infrastructure. The good news is creating new versions and milestones in Bugzilla takes no special trickery, so it _should_ be relatively easy. Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Intencha tomorrow's technology today Ph: 3420 4584 0422236329 35 Prenzler St Upper Mount Gravatt 4122 Australia QLD www.intencha.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bugzilla
Oh, man. No thunder, just emotional devastation. It has been quite an ugly squabble and have made a few non-friends among the Infrastructure folks. Anyways, we need to make an announcement on the site in order to preempt (some of) the confusion among the users. Finally this issue is done with and we can move on with the migration process Evil Comrade Oleg On Mon, 2004-10-11 at 04:46, Adrian Sutton wrote: Hi all, Oleg has done a fantastic job in finally getting HttpClient converted from a component to a real project in bugzilla. There are a couple of things remaining that some help could be used on: 1. Check that everything looks right after the migration (the standard bugzilla installation on nagoya should now show the migrated version). 2. Decide if we now want to convert over to JIRA or stay with Bugzilla. Most of our issues with bugzilla should be solved now that we're a full project, however JIRA is much better supported than Bugzilla so we may want to move anyway. Let me know your thoughts and we'll unleash evil comrade Oleg on the infrastructure team again. :) Three big cheers to Oleg for following through on this. I don't mean to steal the thunder of the announcement but figured I'd keep the messages flowing during the night shift (aka: Australian day time). Regards, Adrian Sutton. -- Intencha tomorrow's technology today Ph: 3420 4584 0422236329 35 Prenzler St Upper Mount Gravatt 4122 Australia QLD www.intencha.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCE] HttpClient is now a separate project in [Bugzilla] issue tracking system
HttpClient project has taken a very important step toward becoming a full-fledged Jakarta level project. From today, HttpClient is a separate project in Apache Bugzilla issue tracking system. It is no longer a component of the Commons project. Please use the following details when filing bug reports for 2.0 and 3.0 branches of HttpClient: Product: HttpClient Component: Commons HttpClient Use the following URL for convenience: http://issues.apache.org/bugzilla/enter_bug.cgi?product=HttpClient All the existing issues, closed and open, are still available under their usual URLs. With HttpClient being a separate project in Bugzilla we will be able to define release versions and target milestones independently from Jakarta Commons Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] HttpClient is now a separate project in [Bugzilla] issue tracking system
Awesome! Nice work Oleg. Mike Oleg Kalnichevski wrote: HttpClient project has taken a very important step toward becoming a full-fledged Jakarta level project. From today, HttpClient is a separate project in Apache Bugzilla issue tracking system. It is no longer a component of the Commons project. Please use the following details when filing bug reports for 2.0 and 3.0 branches of HttpClient: Product: HttpClient Component: Commons HttpClient Use the following URL for convenience: http://issues.apache.org/bugzilla/enter_bug.cgi?product=HttpClient All the existing issues, closed and open, are still available under their usual URLs. With HttpClient being a separate project in Bugzilla we will be able to define release versions and target milestones independently from Jakarta Commons Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Bugzilla] vs [JIRA] revisited
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. http://nagoya.apache.org/jira/browse/INFRA-74 The only fundamental gripe with JIRA that some folks have is that it is not open-source. I do not think we should try to be holier than the Pope himself, since too many projects have already defected to JIRA Religious reasons aside, I also foresee technical difficulties too. Currently (at least with Bugzilla 2.14.2) there appears no way to make a project completely read-only. Submission of new reports can be disabled, but one can still modify the existing bug reports. There is a few options: (1) Ask folks to resubmit their comments in JIRA when important / ignore modifications made in Bugzilla when unimportant. (2) Tweak Bugzilla a little to prevent mutation of existing reports. Note, supposedly Apache Bugzilla is already a fork. So, the real trouble here is to convince the Infrastructure folks to apply a patch, and more importantly reapply it every time Bugzilla is upgraded. Now, the REAL REAL trouble is that it almost took a full scale nuclear conflict between the Evil Russian Empire (me) and the Freedom Alliance (the Infrastructure team) to implement what turned out to be a fairly minor change to get HttpClient promoted to a project status. From now on, I am deeply skeptical about everything that has to do with Bugzilla maintenance. Besides, I may not survive yet another squabble with Noel. (3) Wait until other Jakarta Commons project migrate first. Long may be the wait, though So, what's the popular opinion on that? Non-committers are highly encouraged to voice their opinion too Evil Comrade Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Bugzilla] vs [JIRA] revisited
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
Re: [Bugzilla] vs [JIRA] revisited
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 what else we can do but start hacking on 4.0 branch while 3.0 still goes through its natural development cycle: alpha - beta - rc - release. I sense the work on 4.0 may well commence as early as next month. Basically that will buy us some time, but not much. I certainly want to start the discussion on the 4.0 architecture (at least in broad strokes) very, very soon. This, again, makes the issue of issue tracking system highly important, as we better have a sane road map and reasonably well articulated strategy as soon as people start asking what the heck Jakarta HttpClient 4.0 is all about and how on earth we ended up with 3 API incompatible branches. Oleg On Mon, 2004-10-11 at 16:43, Roland Weber wrote: 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 *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Bugzilla] vs [JIRA] revisited
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 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 what else we can do but start hacking on 4.0 branch while 3.0 still goes through its natural development cycle: alpha - beta - rc - release. I sense the work on 4.0 may well commence as early as next month. Basically that will buy us some time, but not much. I certainly want to start the discussion on the 4.0 architecture (at least in broad strokes) very, very soon. This, again, makes the issue of issue tracking system highly important, as we better have a sane road map and reasonably well articulated strategy as soon as people start asking what the heck Jakarta HttpClient 4.0 is all about and how on earth we ended up with 3 API incompatible branches. Oleg On Mon, 2004-10-11 at 16:43, Roland Weber wrote: 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 *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Bugzilla] vs [JIRA] revisited
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 Jakarta is moving in that direction. Also, if we're going to switch repos and change our package name it would seem like a good time. I agree that it may be difficult to do all these things at once, but I think if we start doing things now it shouldn't be too painful. The next item to move is probably the mailing list. This has been on my TODO list for a while now. I'll email infrastructure tonight and get the ball rolling. Besides, unless we start getting MASSIVELY more feedback on 3.0, I am not sure what else we can do but start hacking on 4.0 branch while 3.0 still goes through its natural development cycle: alpha - beta - rc - release. I sense the work on 4.0 may well commence as early as next month. Basically that will buy us some time, but not much. I certainly want to start the discussion on the 4.0 architecture (at least in broad strokes) very, very soon. Next month seems pretty soon, but I guess you never know. My guess was that it wouldn't happen until January. We definitely want a pretty solid plan before we get started though. This, again, makes the issue of issue tracking system highly important, as we better have a sane road map and reasonably well articulated strategy as soon as people start asking what the heck Jakarta HttpClient 4.0 is all about and how on earth we ended up with 3 API incompatible branches. Yes, I'm not looking forward to 3 supported APIs at the same time. Hopefully 2.0 will be mostly frozen by the time 4.0 gets started. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bugzilla
Hi all, Oleg has done a fantastic job in finally getting HttpClient converted from a component to a real project in bugzilla. There are a couple of things remaining that some help could be used on: 1. Check that everything looks right after the migration (the standard bugzilla installation on nagoya should now show the migrated version). 2. Decide if we now want to convert over to JIRA or stay with Bugzilla. Most of our issues with bugzilla should be solved now that we're a full project, however JIRA is much better supported than Bugzilla so we may want to move anyway. Let me know your thoughts and we'll unleash evil comrade Oleg on the infrastructure team again. :) Three big cheers to Oleg for following through on this. I don't mean to steal the thunder of the announcement but figured I'd keep the messages flowing during the night shift (aka: Australian day time). Regards, Adrian Sutton. -- Intencha tomorrow's technology today Ph: 3420 4584 0422236329 35 Prenzler St Upper Mount Gravatt 4122 Australia QLD www.intencha.com PGP.sig Description: This is a digitally signed message part
[VOTE][RESULT] Migrate HttpClient issue tracking from Bugzilla to Jira
HttpClient project voted in favour of migration from Bugzilla to Jira +1 votes - Jeff Dever jsdever -at- apache.org Ortwin Glück oglueck -at -apache.org Adrian Sutton adrian -at- apache.org Oleg Kalnichevski olegk -at- apache.org Michael Becke mbecke -at- apache.org *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE][RESULT] Migrate HttpClient issue tracking from Bugzilla to Jira
Folks I have filed a request with the infrastructure to migrate HttpClient issue tracking from Bugzilla to Jira http://nagoya.apache.org/jira/browse/INFRA-74 I hope we'll get luckier this time around Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][RESULT] Migrate HttpClient issue tracking from Bugzilla to Jira
Looks like you will indeed get luckier, the status on the report says: Comment by Serge Knystautas [11/May/04 10:24 AM] [ Permlink ] I should be able to get this migrated by tomorrow. Thanks, Sam On Tuesday, May 11, 2004, at 01:22 PM, Kalnichevski, Oleg wrote: Folks I have filed a request with the infrastructure to migrate HttpClient issue tracking from Bugzilla to Jira http://nagoya.apache.org/jira/browse/INFRA-74 I hope we'll get luckier this time around Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira
- Vote: Migrate HttpClient issue tracking from Bugzilla to Jira [X] +1 I am in favor of the proposal, and will help support it. [ ] +0 I am in favor of the proposal, but am unable to help support it. [ ] -0 I am not in favor of the proposal. [ ] -1 I am against this proposal (must include a reason). - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira
Please vote as follows: - Vote: Migrate HttpClient issue tracking from Bugzilla to Jira [ ] +1 I am in favor of the proposal, and will help support it. [ ] +0 I am in favor of the proposal, but am unable to help support it. [ ] -0 I am not in favor of the proposal. [ ] -1 I am against this proposal (must include a reason). - Migration process is described here http://nagoya.apache.org/wiki/apachewiki.cgi?JIRABugzillaMigration Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira
+1 -Original Message- From: Kalnichevski, Oleg Sent: Monday, May 10, 2004 11:03 To: Commons HttpClient Project Subject: [VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira Please vote as follows: - Vote: Migrate HttpClient issue tracking from Bugzilla to Jira [x] +1 I am in favor of the proposal, and will help support it. [ ] +0 I am in favor of the proposal, but am unable to help support it. [ ] -0 I am not in favor of the proposal. [ ] -1 I am against this proposal (must include a reason). - Migration process is described here http://nagoya.apache.org/wiki/apachewiki.cgi?JIRABugzillaMigration Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira
+1 I'm now on the infrastructure list btw and would be happy to take charge of getting this project done (I have no actual administrative powers but I do at least see what's going on). Regards, Adrian Sutton. On 10/05/2004, at 7:03 PM, Kalnichevski, Oleg wrote: Please vote as follows: - Vote: Migrate HttpClient issue tracking from Bugzilla to Jira [ ] +1 I am in favor of the proposal, and will help support it. [ ] +0 I am in favor of the proposal, but am unable to help support it. [ ] -0 I am not in favor of the proposal. [ ] -1 I am against this proposal (must include a reason). - Migration process is described here http://nagoya.apache.org/wiki/apachewiki.cgi?JIRABugzillaMigration Oleg -- Intencha tomorrow's technology today Ph: 38478913 0422236329 Suite 8/29 Oatland Crescent Holland Park West 4121 Australia QLD www.intencha.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira
+1 On May 10, 2004, at 5:03 AM, Kalnichevski, Oleg wrote: Please vote as follows: - Vote: Migrate HttpClient issue tracking from Bugzilla to Jira [ ] +1 I am in favor of the proposal, and will help support it. [ ] +0 I am in favor of the proposal, but am unable to help support it. [ ] -0 I am not in favor of the proposal. [ ] -1 I am against this proposal (must include a reason). - Migration process is described here http://nagoya.apache.org/wiki/apachewiki.cgi?JIRABugzillaMigration Oleg *** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate HttpClient issue tracking from Bugzilla to Jira
+1 Vote: Migrate HttpClient issue tracking from Bugzilla to Jira [x] +1 I am in favor of the proposal, and will help support it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 Jira. Maybe we should consider upgrade to Jira at this point Oleg On Thu, 2004-04-29 at 01:40, Michael Becke wrote: 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 serving us well, but I am really getting discouraged by the lack of support for it. This is not the first request regarding Bugzilla management that received no response of what so ever. I understand that our infrastructure folks have got enough things to worry about but one would at least expect some sort of response within a week. I am afraid there's simply no one interested in maintaining Bugzilla, which makes me think about Jira as the only viable alternative I agree. Bugzilla works well for us, excepting the current problem with us being a commons sub-project. Let's give them a little more time, and if we still don't hear anything we can look into moving to Jira. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 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 Jira. Maybe we should consider upgrade to Jira at this point Oleg On Thu, 2004-04-29 at 01:40, Michael Becke wrote: 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 serving us well, but I am really getting discouraged by the lack of support for it. This is not the first request regarding Bugzilla management that received no response of what so ever. I understand that our infrastructure folks have got enough things to worry about but one would at least expect some sort of response within a week. I am afraid there's simply no one interested in maintaining Bugzilla, which makes me think about Jira as the only viable alternative I agree. Bugzilla works well for us, excepting the current problem with us being a commons sub-project. Let's give them a little more time, and if we still don't hear anything we can look into moving to Jira. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 PROTECTED] can help with administrative changes.
- Scarab is available but AFAIK is not used by many projects. If it
interests you, infrastructure@ is always welcoming volunteers.
- JIRA was installed early this year and I migrate/setup projects as
requested. It handles many projects now, mainly Xerces, james, avalon,
infrastructure, and some incubator projects.
-jsd
Michael Becke wrote:
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 ping to them would be appropriate.
Mike
Oleg Kalnichevski wrote:
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 forwarding this mail to [EMAIL PROTECTED] Shall we
consider the move to Jira? How does everyone feel about it?
Oleg
On Wed, 2004-04-21 at 09:23, Oleg Kalnichevski wrote:
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 (if at all
possible). Please let us know what is a regular procedure with regards
to Bugzilla content migration and if anything can be done on our
side to
assist you in this process
Cheers,
Oleg
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 forwarding this mail to [EMAIL PROTECTED] Shall we
consider the move to Jira? How does everyone feel about it?
Oleg
On Wed, 2004-04-21 at 09:23, Oleg Kalnichevski wrote:
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 (if at all
possible). Please let us know what is a regular procedure with regards
to Bugzilla content migration and if anything can be done on our side to
assist you in this process
Cheers,
Oleg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 ping to them would be appropriate.
Mike
Oleg Kalnichevski wrote:
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 forwarding this mail to [EMAIL PROTECTED] Shall we
consider the move to Jira? How does everyone feel about it?
Oleg
On Wed, 2004-04-21 at 09:23, Oleg Kalnichevski wrote:
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 (if at all
possible). Please let us know what is a regular procedure with regards
to Bugzilla content migration and if anything can be done on our side to
assist you in this process
Cheers,
Oleg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 serving us well, but I am really getting discouraged by the lack of support for it. This is not the first request regarding Bugzilla management that received no response of what so ever. I understand that our infrastructure folks have got enough things to worry about but one would at least expect some sort of response within a week. I am afraid there's simply no one interested in maintaining Bugzilla, which makes me think about Jira as the only viable alternative I agree. Bugzilla works well for us, excepting the current problem with us being a commons sub-project. Let's give them a little more time, and if we still don't hear anything we can look into moving to Jira. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[HttpClient][Bugzilla] Migration to the Jakarta subproject level
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 (if at all
possible). Please let us know what is a regular procedure with regards
to Bugzilla content migration and if anything can be done on our side to
assist you in this process
Cheers,
Oleg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Bugzilla] Commons HttpClient as a top level Bugzilla project
Good day, I am approaching you on behalf of the Jakarta Commons HttpClient project We are wondering if it would be possible to promote Jakarta Commons HttpClient to a top level project in Bugzilla. We would like to be able to set release versions and milestones specific to HttpClient, which is not possible as long as HttpClient remains a sub-component of jakarta-commmons. Please let us know if that's feasible Cheers, Oleg Kalnichevski On Thu, 2004-01-22 at 21:28, Oleg Kalnichevski wrote: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Bugzilla] Commons HttpClient as a top level Bugzilla project
Hi Martin, In all honesty the idea of moving HttpClient out of Jakarta Commons to become a full-fledged Jakarta project has been discussed a while ago on HttpClient developer's list. However, at that time we were not sure if HttpClient merited such a promotion. The decision to offload HttpClient related mail traffic predates most (if not all) current contributors and committers. I personally am not aware of the rationale behind it and I do not know if HttpClient was initially meant to be a Jakarta level project, but simply was not mature enough. Anyways, a request for promotion to Jakarta level may be a very political move. Certainly, we would feel honoured to be considered, but to some HttpClient may be just a utility component and as such appropriately placed in Jakarta commons. On the other hand, based on the mail traffic, Bugzilla content HttpClient has been generating, the size of the community HttpCleint has got, I believe we have long outgrown Jakarta Commons. Martin, how would you advise up to go about this issue? Who shall we approach? Michael, since this is no longer just a Bugzilla issue, I think you, being our project lead, should take over from here Cheers, Oleg On Sat, 2004-01-31 at 22:07, Martin Cooper wrote: To be honest, I think you need to seriously consider moving HttpClient out of Jakarta Commons, either to a full Jakarta project or to a TLP. Already, HttpClient has its own mailing list, and as a result, it has become its own world, with little relation to the rest of Jakarta Commons except in name. If HttpClient has its own mailing list, its own Bugzilla category, and its own separate community, there doesn't seem to be much reason to stay within Jakarta Commons, whereas I see good reasons for it to move out. -- Martin Cooper On Sat, 31 Jan 2004, Oleg Kalnichevski wrote: Good day, I am approaching you on behalf of the Jakarta Commons HttpClient project We are wondering if it would be possible to promote Jakarta Commons HttpClient to a top level project in Bugzilla. We would like to be able to set release versions and milestones specific to HttpClient, which is not possible as long as HttpClient remains a sub-component of jakarta-commmons. Please let us know if that's feasible Cheers, Oleg Kalnichevski On Thu, 2004-01-22 at 21:28, Oleg Kalnichevski wrote: 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Bugzilla] Commons HttpClient as a top level Bugzilla project
Hello Martin, Oleg, On Jan 31, 2004, at 7:01 PM, Martin Cooper wrote: Moving out of Commons and up to your own Jakarta project is internal to Jakarta, so what I would suggest is this: 1) Discuss it and make sure you have agreement within the HttpClient community. You probably should have a vote at some point, unless it's apparent from the outset that everyone is in favour. 2) Write up a proposal, and send it to the Jakarta PMC. It might also be a good idea to CC the commons-dev list, to let the folks there know what's going on. I doubt very much that there will be any dissent on the PMC, since at that point it will be a community decision. 3) Once the PMC is happy, we can get you set up as your own Jakarta project. There are folks on the PMC who should be able to take care of most, if not all, of the details. Anything else you can collate into a list to send to infrastructure@ at that point. These sound like a reasonable set of steps. Let's start this discussion on httpclient dev and see if the HttpClient community is ready to make the move. I think the concept of a project lead is peculiar to the HttpClient component. (IIRC, it was introduced by Jeff Dever quite some time ago, and I guess it stuck.) Obviously, if that's how you'd like to handle it, that's fine with me. ;-) I would assume that Michael is on the PMC, but if not, then you'll need your PMC members to handle any discussion on that list. Though I am considered the HttpClient project lead, this mostly just means that I handle the releases. HttpClient is still managed via consensus. As far as the PMC goes, I am not a member. I do not know if any of the other regular HttpClient committers are either. We may need someone to represent us, if the time comes. Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [HttpClient][Bugzilla] should I stay or should I go?
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:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 21:28 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [HttpClient][Bugzilla] should I stay or should I go?
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:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 21:28 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA vs Bugzilla issue
Folks, What say you, do we migrate HttpClient issue tracking to JIRA or do we stay with Bugzilla? Please let me know your opinion. Oleg On Tue, 2004-01-13 at 20:29, Oleg Kalnichevski wrote: Shall I apply? Any strong opinions to not migrate to JIRA? Oleg On Tue, 2004-01-13 at 20:01, Michael Becke wrote: Yes, I've been following that discussion as well. I'm definitely interested in making the switch to JIRA. Bugzilla has served us pretty well, but I find it somewhat unwieldy at times. Mike On Jan 13, 2004, at 11:44 AM, Kalnichevski, Oleg wrote: There's currently a rather animated discussion 'JIRA vs Bugzilla' going on the commons-dev mailing list. Personally I do not have a strong option on this issue. There's one thing, though, that makes me bring it up here: we are facing the need to massively restructure Bugzilla content related to HttpClient due to the change of the next release version from 2.1 to 3.0. (Funny enough, the way versioning is handled in Bugzilla is being one of the most frequently mentioned motivators for migration to JIRA). My point here, if we ever wanted to migrate to JIRA, now would be the right moment. Let me know what you think (let us not turn it into a religious war currently being waged on the commons-dev, though) Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA vs Bugzilla issue
Oleg Kalnichevski wrote: Folks, What say you, do we migrate HttpClient issue tracking to JIRA or do we stay with Bugzilla? Please let me know your opinion. Oleg Sorry, I have not had the time to take a look at JIRA and I don't know that product at all. All I can say is that I am quite familiar and happy with Bugzilla and I don't miss anything currently. Odi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA vs Bugzilla issue
Thanks for your explanation. So I am okay with moving to JIRA. Now is really a good time, since the number of open bugs is relatively small. What about existing (old) bugs? Can those be migrated somehow automatically? Odi Kalnichevski, Oleg wrote: Odi, One nastiest thing about Bugzilla is its release versioning scheme: the release versions in Bugzilla apply to all components within a project. Since all Commons projects are defined as sub-projects within a project, we cannot have release targets defined specifically for HttpClient. For instance, we can't simply have 2.1 version renamed to 3.0 and 3.0 to 4.0. There may already be other projects using 2.1 tags. We'll have to go through a manual process of reassigning target milestones on all 30 some bug reports. Not to mention asking the Bugzilla admin to create those damn tags for us. JIRA is supposedly free from many of those limitations Basically my original point was, if we ever wanted to migrate, now would be the right time. I am also quite satisfied with Bugzilla, but do find Bugzilla's versioning scheme constraining. Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA vs Bugzilla issue
Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. Thanks Moh -Original Message- From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 6:41 AM To: Jakarta Commons HttpClient mailing list Subject: Re: JIRA vs Bugzilla issue Folks, What say you, do we migrate HttpClient issue tracking to JIRA or do we stay with Bugzilla? Please let me know your opinion. Oleg On Tue, 2004-01-13 at 20:29, Oleg Kalnichevski wrote: Shall I apply? Any strong opinions to not migrate to JIRA? Oleg On Tue, 2004-01-13 at 20:01, Michael Becke wrote: Yes, I've been following that discussion as well. I'm definitely interested in making the switch to JIRA. Bugzilla has served us pretty well, but I find it somewhat unwieldy at times. Mike On Jan 13, 2004, at 11:44 AM, Kalnichevski, Oleg wrote: There's currently a rather animated discussion 'JIRA vs Bugzilla' going on the commons-dev mailing list. Personally I do not have a strong option on this issue. There's one thing, though, that makes me bring it up here: we are facing the need to massively restructure Bugzilla content related to HttpClient due to the change of the next release version from 2.1 to 3.0. (Funny enough, the way versioning is handled in Bugzilla is being one of the most frequently mentioned motivators for migration to JIRA). My point here, if we ever wanted to migrate to JIRA, now would be the right moment. Let me know what you think (let us not turn it into a religious war currently being waged on the commons-dev, though) Oleg -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JIRA vs Bugzilla issue
Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. I do not have all the details, but JIRA is believed to provide some sort of an automated migration path for existing Bugzilla installations. Anyways, if ALL existing bug reports cannot be retained, in my opinion, that would completely defeat the whole migration idea. I'll double-check the possibility of having existing reports migrated with the infrastructure folks, before the final decision is made. I'll keep you posted. Oleg -Original Message- From: Rezaei, Mohammad A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 15:24 To: 'Commons HttpClient Project' Subject: RE: JIRA vs Bugzilla issue Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. Thanks Moh -Original Message- From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 6:41 AM To: Jakarta Commons HttpClient mailing list Subject: Re: JIRA vs Bugzilla issue Folks, What say you, do we migrate HttpClient issue tracking to JIRA or do we stay with Bugzilla? Please let me know your opinion. Oleg On Tue, 2004-01-13 at 20:29, Oleg Kalnichevski wrote: Shall I apply? Any strong opinions to not migrate to JIRA? Oleg On Tue, 2004-01-13 at 20:01, Michael Becke wrote: Yes, I've been following that discussion as well. I'm definitely interested in making the switch to JIRA. Bugzilla has served us pretty well, but I find it somewhat unwieldy at times. Mike On Jan 13, 2004, at 11:44 AM, Kalnichevski, Oleg wrote: There's currently a rather animated discussion 'JIRA vs Bugzilla' going on the commons-dev mailing list. Personally I do not have a strong option on this issue. There's one thing, though, that makes me bring it up here: we are facing the need to massively restructure Bugzilla content related to HttpClient due to the change of the next release version from 2.1 to 3.0. (Funny enough, the way versioning is handled in Bugzilla is being one of the most frequently mentioned motivators for migration to JIRA). My point here, if we ever wanted to migrate to JIRA, now would be the right moment. Let me know what you think (let us not turn it into a religious war currently being waged on the commons-dev, though) Oleg -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA vs Bugzilla issue
Well, I'm not sure how I would recommend going on this decision. So here is my attempt at providing a slightly biased (in favor of Bugzilla) view of the facts. I looked at nagoya.apache.org, and checked out both the Scarab and Jelly installations running there. Random observations: * Bugzilla is designed for a flat product listing. Currently Apache Commons tools are listed as a component of Apache Commons, rather than a top-level project like Commons-HttpClient. Were this changed instead, all of the complaints about not being able to establish coherent milestones and versions would go away. As it is, it seems unfair to compare to JIRA with respect to this issue, because migrating to JIRA will apparently make HttpClient a top level project- thus comparing apples to oranges. * Apache appears to be running Bugzilla 2.14.2. Bugzilla is up to 2.16.4 for their stable build, and 2.17.6 on their testing branch. We use 2.16.4 at my office and I have no complaints with it. I know that there are some nice but subtle improvements with the newer release(s). * JIRA appears to be missing a nice feature of (the newer) Bugzilla, namely that when examining a bug from a list of bugs, you can click Next and Previous to see other bugs, rather than having to go back to the list view. In Mozilla, this actually enables an extra toolbar with next and previous buttons. * JIRA has a significantly cleaner look and feel, most definitely. * JIRA appears to have links to specific responses to issues/bugs. Bugzilla doesn't have this - you can only link to the bug as a whole, so far as I know. * Scarab doesn't let an unregister user browse the reports. This pretty much shoots it down for use in a open source project, for me. I wonder if that is just the way that Apache has it configured. * Scarab appears to be much stricter about its access controls. I'm not sure whether the extra refinement just gets in the way. * As far as the notification emails that JIRA sends out versus the ones that Bugzilla sends, I like the ones that Bugzilla sends better. Far more compact (again a configuration issue?) My suggestion would be to also investigate the possibility of HttpClient being promoted (in Bugzilla only) to a project rather than a component of commons, and also see about having the Bugzilla version updated. -Eric. Kalnichevski, Oleg wrote: Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. I do not have all the details, but JIRA is believed to provide some sort of an automated migration path for existing Bugzilla installations. Anyways, if ALL existing bug reports cannot be retained, in my opinion, that would completely defeat the whole migration idea. I'll double-check the possibility of having existing reports migrated with the infrastructure folks, before the final decision is made. I'll keep you posted. Oleg -Original Message- From: Rezaei, Mohammad A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 15:24 To: 'Commons HttpClient Project' Subject: RE: JIRA vs Bugzilla issue Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. Thanks Moh -Original Message- From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 6:41 AM To: Jakarta Commons HttpClient mailing list Subject: Re: JIRA vs Bugzilla issue Folks, What say you, do we migrate HttpClient issue tracking to JIRA or do we stay with Bugzilla? Please let me know your opinion. Oleg On Tue, 2004-01-13 at 20:29, Oleg Kalnichevski wrote: Shall I apply? Any strong opinions to not migrate to JIRA? Oleg On Tue, 2004-01-13 at 20:01, Michael Becke wrote: Yes, I've been following that discussion as well. I'm definitely interested in making the switch to JIRA. Bugzilla has served us pretty well, but I find it somewhat unwieldy at times. Mike On Jan 13, 2004, at 11:44 AM, Kalnichevski, Oleg wrote: There's currently a rather animated discussion 'JIRA vs Bugzilla' going on the commons-dev mailing list. Personally I do not have a strong option on this issue. There's one thing, though, that makes me bring it up here: we are facing the need to massively restructure Bugzilla content related to HttpClient due to the change of the next release version from 2.1 to 3.0. (Funny enough, the way versioning is handled in Bugzilla is being one of the most frequently mentioned motivators for migration to JIRA). My point here, if we ever wanted to migrate to JIRA, now would be the right moment. Let me know what you think (let us not turn it into a religious war currently being waged on the commons-dev, though) Oleg
RE: JIRA vs Bugzilla issue
My suggestion would be to also investigate the possibility of HttpClient being promoted (in Bugzilla only) to a project rather than a component of commons, and also see about having the Bugzilla version updated. Eric, I think it's a brilliant idea. It does make sense that HttpClient gets treated slightly differently than other peer Commons sub-projects due to a higher volume of bug reports/feature requests we get. Out of 100 some open bug reports in Jakarta-Commons project 30 some are ours. When first 3.0-alpha comes out, this number is quite likely to increase substantially. Unfortunately, I do know how difficult that would be (if technically feasible at all). As it is, it seems unfair to compare to JIRA with respect to this issue, because migrating to JIRA will apparently make HttpClient a top level project- thus comparing apples to oranges. I believe JIRA can assign a unique versioning scheme on a per component (in Bugzilla parlance sub-project) basis. But you have a point here, anyways. Oleg -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 18:09 To: Commons HttpClient Project Subject: Re: JIRA vs Bugzilla issue Well, I'm not sure how I would recommend going on this decision. So here is my attempt at providing a slightly biased (in favor of Bugzilla) view of the facts. I looked at nagoya.apache.org, and checked out both the Scarab and Jelly installations running there. Random observations: * Bugzilla is designed for a flat product listing. Currently Apache Commons tools are listed as a component of Apache Commons, rather than a top-level project like Commons-HttpClient. Were this changed instead, all of the complaints about not being able to establish coherent milestones and versions would go away. As it is, it seems unfair to compare to JIRA with respect to this issue, because migrating to JIRA will apparently make HttpClient a top level project- thus comparing apples to oranges. * Apache appears to be running Bugzilla 2.14.2. Bugzilla is up to 2.16.4 for their stable build, and 2.17.6 on their testing branch. We use 2.16.4 at my office and I have no complaints with it. I know that there are some nice but subtle improvements with the newer release(s). * JIRA appears to be missing a nice feature of (the newer) Bugzilla, namely that when examining a bug from a list of bugs, you can click Next and Previous to see other bugs, rather than having to go back to the list view. In Mozilla, this actually enables an extra toolbar with next and previous buttons. * JIRA has a significantly cleaner look and feel, most definitely. * JIRA appears to have links to specific responses to issues/bugs. Bugzilla doesn't have this - you can only link to the bug as a whole, so far as I know. * Scarab doesn't let an unregister user browse the reports. This pretty much shoots it down for use in a open source project, for me. I wonder if that is just the way that Apache has it configured. * Scarab appears to be much stricter about its access controls. I'm not sure whether the extra refinement just gets in the way. * As far as the notification emails that JIRA sends out versus the ones that Bugzilla sends, I like the ones that Bugzilla sends better. Far more compact (again a configuration issue?) My suggestion would be to also investigate the possibility of HttpClient being promoted (in Bugzilla only) to a project rather than a component of commons, and also see about having the Bugzilla version updated. -Eric. Kalnichevski, Oleg wrote: Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. I do not have all the details, but JIRA is believed to provide some sort of an automated migration path for existing Bugzilla installations. Anyways, if ALL existing bug reports cannot be retained, in my opinion, that would completely defeat the whole migration idea. I'll double-check the possibility of having existing reports migrated with the infrastructure folks, before the final decision is made. I'll keep you posted. Oleg -Original Message- From: Rezaei, Mohammad A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 15:24 To: 'Commons HttpClient Project' Subject: RE: JIRA vs Bugzilla issue Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. Thanks Moh -Original Message- From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 6:41 AM To: Jakarta Commons HttpClient mailing list Subject: Re: JIRA vs Bugzilla issue Folks, What say you, do we migrate HttpClient issue tracking to JIRA
Re: JIRA vs Bugzilla issue
I agree these are some good idea Eric. The one main problem, as it has been discussed on commons-dev, is that no-one seems to be interested in maintaining Bugzilla. This is why we are using such an old version. This seems to be a key issue for some of the other commons projects. Mike On Jan 21, 2004, at 12:26 PM, Kalnichevski, Oleg wrote: My suggestion would be to also investigate the possibility of HttpClient being promoted (in Bugzilla only) to a project rather than a component of commons, and also see about having the Bugzilla version updated. Eric, I think it's a brilliant idea. It does make sense that HttpClient gets treated slightly differently than other peer Commons sub-projects due to a higher volume of bug reports/feature requests we get. Out of 100 some open bug reports in Jakarta-Commons project 30 some are ours. When first 3.0-alpha comes out, this number is quite likely to increase substantially. Unfortunately, I do know how difficult that would be (if technically feasible at all). As it is, it seems unfair to compare to JIRA with respect to this issue, because migrating to JIRA will apparently make HttpClient a top level project- thus comparing apples to oranges. I believe JIRA can assign a unique versioning scheme on a per component (in Bugzilla parlance sub-project) basis. But you have a point here, anyways. Oleg -Original Message- From: Eric Johnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 18:09 To: Commons HttpClient Project Subject: Re: JIRA vs Bugzilla issue Well, I'm not sure how I would recommend going on this decision. So here is my attempt at providing a slightly biased (in favor of Bugzilla) view of the facts. I looked at nagoya.apache.org, and checked out both the Scarab and Jelly installations running there. Random observations: * Bugzilla is designed for a flat product listing. Currently Apache Commons tools are listed as a component of Apache Commons, rather than a top-level project like Commons-HttpClient. Were this changed instead, all of the complaints about not being able to establish coherent milestones and versions would go away. As it is, it seems unfair to compare to JIRA with respect to this issue, because migrating to JIRA will apparently make HttpClient a top level project- thus comparing apples to oranges. * Apache appears to be running Bugzilla 2.14.2. Bugzilla is up to 2.16.4 for their stable build, and 2.17.6 on their testing branch. We use 2.16.4 at my office and I have no complaints with it. I know that there are some nice but subtle improvements with the newer release(s). * JIRA appears to be missing a nice feature of (the newer) Bugzilla, namely that when examining a bug from a list of bugs, you can click Next and Previous to see other bugs, rather than having to go back to the list view. In Mozilla, this actually enables an extra toolbar with next and previous buttons. * JIRA has a significantly cleaner look and feel, most definitely. * JIRA appears to have links to specific responses to issues/bugs. Bugzilla doesn't have this - you can only link to the bug as a whole, so far as I know. * Scarab doesn't let an unregister user browse the reports. This pretty much shoots it down for use in a open source project, for me. I wonder if that is just the way that Apache has it configured. * Scarab appears to be much stricter about its access controls. I'm not sure whether the extra refinement just gets in the way. * As far as the notification emails that JIRA sends out versus the ones that Bugzilla sends, I like the ones that Bugzilla sends better. Far more compact (again a configuration issue?) My suggestion would be to also investigate the possibility of HttpClient being promoted (in Bugzilla only) to a project rather than a component of commons, and also see about having the Bugzilla version updated. -Eric. Kalnichevski, Oleg wrote: Is there an automatic way to move the current issues over to JIRA? The open bugs are important, but the closed ones also contain a wealth of information. I do not have all the details, but JIRA is believed to provide some sort of an automated migration path for existing Bugzilla installations. Anyways, if ALL existing bug reports cannot be retained, in my opinion, that would completely defeat the whole migration idea. I'll double-check the possibility of having existing reports migrated with the infrastructure folks, before the final decision is made. I'll keep you posted. Oleg -Original Message- From: Rezaei, Mohammad A. [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 15:24 To: 'Commons HttpClient Project' Subject: RE: JIRA vs Bugzilla issue Is there an automatic way to move the current issues over to JIRA? The open bugs are important
Re: JIRA vs Bugzilla issue
Yes, I've been following that discussion as well. I'm definitely interested in making the switch to JIRA. Bugzilla has served us pretty well, but I find it somewhat unwieldy at times. Mike On Jan 13, 2004, at 11:44 AM, Kalnichevski, Oleg wrote: There's currently a rather animated discussion 'JIRA vs Bugzilla' going on the commons-dev mailing list. Personally I do not have a strong option on this issue. There's one thing, though, that makes me bring it up here: we are facing the need to massively restructure Bugzilla content related to HttpClient due to the change of the next release version from 2.1 to 3.0. (Funny enough, the way versioning is handled in Bugzilla is being one of the most frequently mentioned motivators for migration to JIRA). My point here, if we ever wanted to migrate to JIRA, now would be the right moment. Let me know what you think (let us not turn it into a religious war currently being waged on the commons-dev, though) Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JIRA vs Bugzilla issue
Shall I apply? Any strong opinions to not migrate to JIRA? Oleg On Tue, 2004-01-13 at 20:01, Michael Becke wrote: Yes, I've been following that discussion as well. I'm definitely interested in making the switch to JIRA. Bugzilla has served us pretty well, but I find it somewhat unwieldy at times. Mike On Jan 13, 2004, at 11:44 AM, Kalnichevski, Oleg wrote: There's currently a rather animated discussion 'JIRA vs Bugzilla' going on the commons-dev mailing list. Personally I do not have a strong option on this issue. There's one thing, though, that makes me bring it up here: we are facing the need to massively restructure Bugzilla content related to HttpClient due to the change of the next release version from 2.1 to 3.0. (Funny enough, the way versioning is handled in Bugzilla is being one of the most frequently mentioned motivators for migration to JIRA). My point here, if we ever wanted to migrate to JIRA, now would be the right moment. Let me know what you think (let us not turn it into a religious war currently being waged on the commons-dev, though) Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is Bugzilla mail broken? was [VFS|HttpClient] Re: [VFS] Crashes in getContent()
It seems that Bugzilla is not sending email for some reason. Anyone have some insight into this? Mike Adam R. B. Jack wrote: I updated the bug database (I believe) so this is posted there. FWIIW: I do not believe I am receiving e-mails from the bug tracker. Are other folks? Did you get my update? regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
