You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Pier Fumagalli <pi...@betaversion.org> on 2005/10/11 12:43:01 UTC
[VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Ok, there we go, here's the vote...
[ ] +1 Yes please, let's move all our bugs to Jira and set it up
to work in the following way:
Statuses (workflow running accordingly):
- OPEN
- REOPENED
- CLOSED
- WAITING FOR FEEDBACK
Issue Types:
- BUG
- NEW FEATURE
- IMPROVEMENT
- TEST
- WISH
- TASK
- ROADMAP
Components:
- One per block
- Core
- Other
Cocoon "Part":
- Sitemap components
- Generic components
- Components and Roles Configurations
- Cocoon forms
- Flow (Flowscript, Javaflow, ...)
- Samples
- Sitemaps
- Build Environment
- Core Java
- Documentation
Version/Status/Resolutions/Priorities:
- Jira defaults
[ ] -/+0 I could care less what issue tracking system we use
[ ] -1 No, I want to keep using Bugzilla because ....
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 11 Oct 2005, at 14:03, Reinhard Poetz wrote:
> Pier Fumagalli wrote:
>
>> Ok, there we go, here's the vote...
>> [X] +1 Yes please, let's move all our bugs to Jira and set it up
>> to work in the following way:
>>
>> Cocoon "Part":
>> - Sitemap components
>> - Generic components
>> - Components and Roles Configurations
>> - Cocoon forms
>> - Flow (Flowscript, Javaflow, ...)
>> - Samples
>> - Sitemaps
>> - Build Environment
>> - Core Java
>> - Documentation
>>
>
> I'm not sure about the "parts". Do we really need all of them?
> IIUC the concept of "part" correctly, having
>
> - code
> - documentation
> - build environment
>
> should be enough. Note that samples will (have) become blocks on
> their own.
> The other part types don't make much sense to me.
It's to identify errors occurring in a specific part of a block... If
we take samples out of the picture, a block might with some forms
(let's assume the Captcha block provides a sitemap using CForms, for
example). So, I could target a bug, issue, task, whatever to a
specific block (Captcha block, this is in the components) and
subtarget it to "Sitemap" and "Forms" in the "part"...
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Reinhard Poetz <re...@apache.org>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
>
> [X] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
> Cocoon "Part":
> - Sitemap components
> - Generic components
> - Components and Roles Configurations
> - Cocoon forms
> - Flow (Flowscript, Javaflow, ...)
> - Samples
> - Sitemaps
> - Build Environment
> - Core Java
> - Documentation
I'm not sure about the "parts". Do we really need all of them? IIUC the concept
of "part" correctly, having
- code
- documentation
- build environment
should be enough. Note that samples will (have) become blocks on their own.
The other part types don't make much sense to me.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Stefano Mazzocchi <st...@apache.org>.
Carsten Ziegeler wrote:
> Pier Fumagalli wrote:
>
>>Ok, there we go, here's the vote...
>>
>>[X] +1 Yes please, let's move all our bugs to Jira and set it up
>> to work in the following way:
>>
+1
--
Stefano, who has a serious problem with how bugzilla looks
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Carsten Ziegeler <cz...@apache.org>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
>
> [X] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
>
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Jorg Heymans <jh...@domek.be>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
>
call me old fashioned but i like bugzilla. For some reason we are not
able to maximize on its features while projects more complex than Cocoon
obviously are.
In the end I guess i'm in favour of anything that will get us to care
more about issue list management, so I'm really curious to see if this
will help (can we switch back if it doesn't? :P )
so: -0.5 for old times sake!
Jorg
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by David Crossley <cr...@apache.org>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
0 ... i don't care which issue tracking system we use.
-David
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
>
> [X] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
>
> Statuses (workflow running accordingly):
> - OPEN
> - REOPENED
> - CLOSED
> - WAITING FOR FEEDBACK
>
> Issue Types:
> - BUG
> - NEW FEATURE
> - IMPROVEMENT
> - TEST
> - WISH
> - TASK
> - ROADMAP
>
> Components:
> - One per block
> - Core
> - Other
>
> Cocoon "Part":
> - Sitemap components
> - Generic components
> - Components and Roles Configurations
> - Cocoon forms
> - Flow (Flowscript, Javaflow, ...)
> - Samples
> - Sitemaps
> - Build Environment
> - Core Java
> - Documentation
>
> Version/Status/Resolutions/Priorities:
> - Jira defaults
>
> [ ] -/+0 I could care less what issue tracking system we use
>
> [ ] -1 No, I want to keep using Bugzilla because ....
--
Leszek Gawron lgawron@mobilebox.pl
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Joerg Heinicke <jo...@gmx.de>.
Pier Fumagalli <pier <at> betaversion.org> writes:
> [X] -1 No, I want to keep using Bugzilla because ....
... I'm much more used to it. But I will probably also learn to use Jira if the
community decides to switch, what it looks like at the moment.
Jörg
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Ralph Goers <Ra...@dslextreme.com>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
>
> [ ] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
>
> Statuses (workflow running accordingly):
> - OPEN
> - REOPENED
> - CLOSED
> - WAITING FOR FEEDBACK
>
> Issue Types:
> - BUG
> - NEW FEATURE
> - IMPROVEMENT
> - TEST
> - WISH
> - TASK
> - ROADMAP
>
> Components:
> - One per block
> - Core
> - Other
>
> Cocoon "Part":
> - Sitemap components
> - Generic components
> - Components and Roles Configurations
> - Cocoon forms
> - Flow (Flowscript, Javaflow, ...)
> - Samples
> - Sitemaps
> - Build Environment
> - Core Java
> - Documentation
>
> Version/Status/Resolutions/Priorities:
> - Jira defaults
>
> [ ] -/+0 I could care less what issue tracking system we use
>
> [ ] -1 No, I want to keep using Bugzilla because ....
+0 I haven't used Jira. As long as what we use is blessed by infra
(and I know Jira is) then I'll go with the flow.
Ralph
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by hepabolu <he...@gmail.com>.
Gianugo Rabellino wrote:
> On 10/11/05, Pier Fumagalli <pi...@betaversion.org> wrote:
>
>>Ok, there we go, here's the vote...
>>
>>[ ] +1 Yes please, let's move all our bugs to Jira and set it up
>> to work in the following way:
>
>
> +1
+1
Helma
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Gianugo Rabellino <gi...@gmail.com>.
On 10/11/05, Pier Fumagalli <pi...@betaversion.org> wrote:
> Ok, there we go, here's the vote...
>
> [ ] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
+1
Ciao,
--
Gianugo
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Joerg Heinicke <jo...@gmx.de>.
On 13.10.2005 23:41, Pier Fumagalli wrote:
> Logins are copied from Bugzilla with the issues they're associated with
> (which is cool, but that means that if you registered with a different
> email address from Bugzilla, I'll have to go in and merge the
> accounts). But for users, that's totally transparent.
>
> Regarding the bugs themselves, I can write a simple script closing all
> moved bugs with a link to the new bug in Jira as a comment (of course,
> after the data-transfer is complete)
Sounds good enough to address my concerns :)
Jörg
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Jeff Turner <je...@apache.org>.
On Fri, Oct 14, 2005 at 05:09:50PM +0200, Bertrand Delacretaz wrote:
> Le 14 oct. 05, à 16:01, Bertrand Delacretaz a écrit :
>
> > ...I don't know if jira is as good as bugzilla for mass operations
> > (i.e. "set all open issues which were entered before Sept 1st to LATER
> > / P5), I'll check as soon as it is back...
>
> I've checked - there are nice bulk operations, but at first glance they
> don't seem to allow the issue state to be changed.
You can't bulk change status, but given a list of issues the change can
be scripted [1].
--Jeff
> -Bertrand
[1] RSS -> XSLT -> Jelly - see
http://www.atlassian.com/software/jira/docs/latest/jelly.html#TransitionWorkflow
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 14 oct. 05, à 16:01, Bertrand Delacretaz a écrit :
> ...I don't know if jira is as good as bugzilla for mass operations
> (i.e. "set all open issues which were entered before Sept 1st to LATER
> / P5), I'll check as soon as it is back...
I've checked - there are nice bulk operations, but at first glance they
don't seem to allow the issue state to be changed.
I'll have another look and maybe suggest a different way of setting the
issues to "awaiting reconfirmation".
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 14 Oct 2005, at 15:58, Peter Hunsberger wrote:
>> The only downside is that people need to create an account jira
>> first,
>> before they can confirm or close their issues. But I agree that it's
>> good to expose people to the new system.
>>
>
> If they care enought about the issue, then they'll need a new account
> at some point anyway?
Nope, the account is created for them automatically by the import. I
can't confirm if passwords are preserved or one has re-enter the
password, but all accounts that have something to do with bugs are
copied.
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Peter Hunsberger <pe...@gmail.com>.
On 10/14/05, Bertrand Delacretaz <bd...@apache.org> wrote:
> Le 14 oct. 05, à 15:46, Peter Hunsberger a écrit :
<snip/>
>
> a) move issues to jira first, set bugzilla readonly
>
> b) do the cleanup in jira, which will send the emails to people with
> links to jira
>
> c) people go to jira to confirm or close the issue.
> The issue includes a backlink to the old bugzilla issue (according to
> Jeff Turner elsewhere in this thread, but
> http://issues.apache.org/jira/ is down currently, I cannot check) in
> case they want to check the info.
>
> Is that what you mean?
Yupp, you've got it.
> The only downside is that people need to create an account jira first,
> before they can confirm or close their issues. But I agree that it's
> good to expose people to the new system.
If they care enought about the issue, then they'll need a new account
at some point anyway?
> I don't know if jira is as good as bugzilla for mass operations (i.e.
> "set all open issues which were entered before Sept 1st to LATER / P5),
> I'll check as soon as it is back.
Got me...
> > ...BTW personally; "bug amnesty" sounds strange, I don't think it
> > really
> > conveys what you are trying to achieve...
>
> The name's been changed to "bugzilla issues cleanup" since, see [1]
>
Yes, I spotted that after my first e-mail. Sounds better...
--
Peter Hunsberger
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by hepabolu <he...@gmail.com>.
Bertrand Delacretaz wrote:
> Let me reformulate, I like the idea:
> a) move issues to jira first, set bugzilla readonly
>
> b) do the cleanup in jira, which will send the emails to people with
> links to jira
>
> c) people go to jira to confirm or close the issue.
> The issue includes a backlink to the old bugzilla issue (according to
> Jeff Turner elsewhere in this thread, but http://issues.apache.org/jira/
> is down currently, I cannot check) in case they want to check the info.
>
> Is that what you mean?
I like this idea. You avoid the problem that people are reminded about
bugs in a system that subsequently is not used any more. It also
(partly) clarifies the bug cleanup operation: starting off with a
"clean" slate.
So I'm +1 for this order.
Bye, Helma
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 14 oct. 05, à 15:46, Peter Hunsberger a écrit :
> ....Following this thread, I wonder if if might not work well to
> combine
> the move to Jira with the so called "bug amnesty"? You'd e-mail
> everyone with an open bug that it was being moved to the new system
> and if they where still interested in it they should re-open it in the
> new system. You'd have to give them the link or number to find it in
> the new system, but by re-opening it you'd get what ever e-mail was
> given on the re-opened bug (force them to enter one perhaps?) and the
> users would have the new number (and be exposed to the new system)....
Let me reformulate, I like the idea:
a) move issues to jira first, set bugzilla readonly
b) do the cleanup in jira, which will send the emails to people with
links to jira
c) people go to jira to confirm or close the issue.
The issue includes a backlink to the old bugzilla issue (according to
Jeff Turner elsewhere in this thread, but
http://issues.apache.org/jira/ is down currently, I cannot check) in
case they want to check the info.
Is that what you mean?
The only downside is that people need to create an account jira first,
before they can confirm or close their issues. But I agree that it's
good to expose people to the new system.
I don't know if jira is as good as bugzilla for mass operations (i.e.
"set all open issues which were entered before Sept 1st to LATER / P5),
I'll check as soon as it is back.
> ...BTW personally; "bug amnesty" sounds strange, I don't think it
> really
> conveys what you are trying to achieve...
The name's been changed to "bugzilla issues cleanup" since, see [1]
-Bertrand
[1] http://marc.theaimsgroup.com/?t=112929331400001&r=1&w=2
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Peter Hunsberger <pe...@gmail.com>.
On 10/14/05, Bertrand Delacretaz <bd...@apache.org> wrote:
> Le 13 oct. 05, à 23:41, Pier Fumagalli a écrit :
> > ...Regarding the bugs themselves, I can write a simple script closing
> > all moved bugs with a link to the new bug in Jira as a comment (of
> > course, after the data-transfer is complete)..
>
> Sounds good, and combined with the "search by bugzilla issue ID" that
> Jeff Turner mentioned, we'll be fine.
Following this thread, I wonder if if might not work well to combine
the move to Jira with the so called "bug amnesty"? You'd e-mail
everyone with an open bug that it was being moved to the new system
and if they where still interested in it they should re-open it in the
new system. You'd have to give them the link or number to find it in
the new system, but by re-opening it you'd get what ever e-mail was
given on the re-opened bug (force them to enter one perhaps?) and the
users would have the new number (and be exposed to the new system).
One mass e-mailing (for conversion and amnesty) instead of two (one
for conversion and one for amnesty).
BTW personally; "bug amnesty" sounds strange, I don't think it really
conveys what you are trying to achieve...
--
Peter Hunsberger
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 13 oct. 05, à 23:41, Pier Fumagalli a écrit :
> ...Regarding the bugs themselves, I can write a simple script closing
> all moved bugs with a link to the new bug in Jira as a comment (of
> course, after the data-transfer is complete)..
Sounds good, and combined with the "search by bugzilla issue ID" that
Jeff Turner mentioned, we'll be fine.
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 13 Oct 2005, at 22:30, Joerg Heinicke wrote:
> On 13.10.2005 23:11, Bertrand Delacretaz wrote:
>>
>>> ...You introduce another problem with this process: Current
>>> owners got sent a bugzilla mail about closure of their bug. If
>>> they want to reopen it later they don't know where to do it...
>>>
>> There must be a way to find issues in jira later based on a
>> bugzilla issue number - there are many links to bugzilla issues
>> floating around, losing them would be a problem.
>>
>
> But the reporter must get to know that the bug has actually been
> moved to Jira - be it with the same issue number or not. Just
> adding a common note to bugzilla might lead to nothing: "Now I have
> to search for my bug in another system? Bah, forget it! I'm to lazy
> to care." Providing a correct link to the new system directly
> jumping to the corresponding issue must be the least. Even then
> many people might be to lazy to care about their bug (new login?,
> new system they don't know, etc.).
Logins are copied from Bugzilla with the issues they're associated
with (which is cool, but that means that if you registered with a
different email address from Bugzilla, I'll have to go in and merge
the accounts). But for users, that's totally transparent.
Regarding the bugs themselves, I can write a simple script closing
all moved bugs with a link to the new bug in Jira as a comment (of
course, after the data-transfer is complete)
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Joerg Heinicke <jo...@gmx.de>.
On 13.10.2005 23:11, Bertrand Delacretaz wrote:
>> ...You introduce another problem with this process: Current owners got
>> sent a bugzilla mail about closure of their bug. If they want to
>> reopen it later they don't know where to do it...
>
> There must be a way to find issues in jira later based on a bugzilla
> issue number - there are many links to bugzilla issues floating around,
> losing them would be a problem.
But the reporter must get to know that the bug has actually been moved
to Jira - be it with the same issue number or not. Just adding a common
note to bugzilla might lead to nothing: "Now I have to search for my bug
in another system? Bah, forget it! I'm to lazy to care." Providing a
correct link to the new system directly jumping to the corresponding
issue must be the least. Even then many people might be to lazy to care
about their bug (new login?, new system they don't know, etc.).
Jörg
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 14 Oct 2005, at 02:08, Jeff Turner wrote:
> It's not possible to directly keep IDs, but it's fairly easy to
> find Jira
> issues by their old Bugzilla ID. On the Jira front page, there is a
> 'Search by Bugzilla ID' box:
>
> http://issues.apache.org/jira/
>
> Eg. searching for bug 8017 gets you to the imported Jira issue,
> http://issues.apache.org/jira/browse/XALANJ-959
Or more easily:
http://issues.apache.org/jira/bugzillasearch.jsp?id=8017
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Jeff Turner <je...@apache.org>.
On Thu, Oct 13, 2005 at 11:11:12PM +0200, Bertrand Delacretaz wrote:
> Le 13 oct. 05, à 22:53, Joerg Heinicke a écrit :
>
> > ...You introduce another problem with this process: Current owners got
> > sent a bugzilla mail about closure of their bug. If they want to
> > reopen it later they don't know where to do it...
>
> There must be a way to find issues in jira later based on a bugzilla
> issue number - there are many links to bugzilla issues floating around,
> losing them would be a problem.
>
> Does anyone know if there is a way to keep issue numbers during
> migration, so that for example
> http://issues.apache.org/bugzilla/show_bug.cgi?id=28102
> would then be found at
> http://issues.apache.org/jira/browse/COCOON-28102
> ?
It's not possible to directly keep IDs, but it's fairly easy to find Jira
issues by their old Bugzilla ID. On the Jira front page, there is a
'Search by Bugzilla ID' box:
http://issues.apache.org/jira/
Eg. searching for bug 8017 gets you to the imported Jira issue,
http://issues.apache.org/jira/browse/XALANJ-959
Imported issues also have a backlink to the Bugzilla bug they came from.
> http://www.atlassian.com/software/jira/docs/v2.4.1/bugzilla_import.html
> says nothing about that.
The latest version of that page has more info:
http://www.atlassian.com/software/jira/docs/latest/bugzilla_import.html#Searching+by+Bugzilla+ID
--Jeff
> > ...If we do the move to Jira we should postpone the closure of the
> > bugs, so that the reporters get at least correct mails which are not
> > invalid after 2 weeks...
>
> This would be an option, but anyway we have to think about this mapping
> of issue numbers.
>
> -Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 13 oct. 05, à 22:53, Joerg Heinicke a écrit :
> ...You introduce another problem with this process: Current owners got
> sent a bugzilla mail about closure of their bug. If they want to
> reopen it later they don't know where to do it...
There must be a way to find issues in jira later based on a bugzilla
issue number - there are many links to bugzilla issues floating around,
losing them would be a problem.
Does anyone know if there is a way to keep issue numbers during
migration, so that for example
http://issues.apache.org/bugzilla/show_bug.cgi?id=28102
would then be found at
http://issues.apache.org/jira/browse/COCOON-28102
?
http://www.atlassian.com/software/jira/docs/v2.4.1/bugzilla_import.html
says nothing about that.
> ...If we do the move to Jira we should postpone the closure of the
> bugs, so that the reporters get at least correct mails which are not
> invalid after 2 weeks...
This would be an option, but anyway we have to think about this mapping
of issue numbers.
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Joerg Heinicke <jo...@gmx.de>.
On 13.10.2005 08:14, Bertrand Delacretaz wrote:
> +1 BUT - I'm going to start a vote about
> http://wiki.apache.org/cocoon/BugzillaIssuesCleanup, to do a big cleanup
> in the next two weeks, so it would be better to wait until this is done.
>
> I expect to start the vote tonight or tomorrow morning when I find time,
> and start the cleanup process monday by changing the state of issues,
> which will send mails to bug owners and reporters.
>
> What do you think? If it's ok for you to do it after the cleanup, I'll
> add this info in the cleanup message ("we're moving to jira and would
> like to cleanup our issues list before"), and ping you when we're done
> with the cleanup.
You introduce another problem with this process: Current owners got sent
a bugzilla mail about closure of their bug. If they want to reopen it
later they don't know where to do it.
If we do the move to Jira we should postpone the closure of the bugs, so
that the reporters get at least correct mails which are not invalid
after 2 weeks.
Jörg
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 19 Oct 2005, at 19:20, Bertrand Delacretaz wrote:
> Le 19 oct. 05, à 19:45, Pier Fumagalli a écrit :
>
>> ...There is a flag "Closed for bug entry" on Bugzilla, which is
>> settable on a per-product basis, I think that will prevent anyone
>> to post new bugs, but we can't put in a "MOVED_TO_JIRA" state
>> (that requires changes in the database, AFAIK), so "WONTFIX" or
>> "LATER" are probably our best options...
>
> Sounds good, keep us posted when you have time to play!
I can play on Saturday! :-) I'll start it then!
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 19 oct. 05, à 19:45, Pier Fumagalli a écrit :
> ...There is a flag "Closed for bug entry" on Bugzilla, which is
> settable on a per-product basis, I think that will prevent anyone to
> post new bugs, but we can't put in a "MOVED_TO_JIRA" state (that
> requires changes in the database, AFAIK), so "WONTFIX" or "LATER" are
> probably our best options...
Sounds good, keep us posted when you have time to play!
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 19 Oct 2005, at 07:46, Bertrand Delacretaz wrote:
> Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
>
>> ...I was waiting for a closure on the "REQ Fixing really old bugs"
>> thread before proposing a timeline, it definitely makes sense to
>> wait for the cleanup to be complete....
>
> Peter's idea of doing the cleanup in Jira makes a lot of sense [1],
> I think you can go ahead with the move, and we'll do the cleanup
> there.
Ok, then... Let me check with the wife what our week-end plans are (I
think she's working, so, I'm free to play, but it's better to triple
check), but if noone shouts STOP before friday night, I'll go ahead
and move the bugs then...
There is a flag "Closed for bug entry" on Bugzilla, which is settable
on a per-product basis, I think that will prevent anyone to post new
bugs, but we can't put in a "MOVED_TO_JIRA" state (that requires
changes in the database, AFAIK), so "WONTFIX" or "LATER" are probably
our best options.
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
> ...I was waiting for a closure on the "REQ Fixing really old bugs"
> thread before proposing a timeline, it definitely makes sense to wait
> for the cleanup to be complete....
Peter's idea of doing the cleanup in Jira makes a lot of sense [1], I
think you can go ahead with the move, and we'll do the cleanup there.
One thing that we haven't discussed IIRC: can we lock the old bugzilla
issues after the move? As the bugzilla instance is shared between many
projects I don't know how to do that.
What I could do is create a script to add a comment like "This issue
has moved to Jira, see
http://issues.apache.org/jira/bugzillasearch.jsp?id=NNNN" with
NNNN=bugzilla issue number, to all bugzilla issues, and set them to
WONTFIX or to a new MOVED_TO_JIRA state.
But maybe someone has a better idea?
-Bertrand
[1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=112929764310413&w=2
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 13 oct. 05, à 16:51, Vadim Gritsenko a écrit :
> Bertrand Delacretaz wrote:
>> Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
>>> ...In the meantime, I'm going to set-up Jira with statuses and
>>> workflows. And after the cleanup is done, we can move all
>>> outstanding issues over...
>
> Shouldn't we move *all* issues to Jira - so that fixed/closed remain
> searchable?...
Yes, sure, sorry I was unclear. All issues must move, even closed ones.
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Bertrand Delacretaz wrote:
> Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
>
>> ...In the meantime, I'm going to set-up Jira with statuses and
>> workflows. And after the cleanup is done, we can move all outstanding
>> issues over...
Shouldn't we move *all* issues to Jira - so that fixed/closed remain searchable?
I see here an analogue between cvs->svn and bugzilla->jira: we have not migrated
HEAD only, but all revisions, so that in svn you have access to history. We
should do same for bugzilla->jira case. WDYT?
Vadim
> Cool, thanks.
> -Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 13 oct. 05, à 10:42, Pier Fumagalli a écrit :
> ...In the meantime, I'm going to set-up Jira with statuses and
> workflows. And after the cleanup is done, we can move all outstanding
> issues over...
Cool, thanks.
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 13 Oct 2005, at 07:14, Bertrand Delacretaz wrote:
> Le 11 oct. 05, à 12:43, Pier Fumagalli a écrit :
>
>
>> Ok, there we go, here's the vote...
>>
>> [ ] +1 Yes please, let's move all our bugs to Jira...
>>
>
> +1 BUT - I'm going to start a vote about http://wiki.apache.org/
> cocoon/BugzillaIssuesCleanup, to do a big cleanup in the next two
> weeks, so it would be better to wait until this is done.
Absolutely... I was waiting for a closure on the "REQ Fixing really
old bugs" thread before proposing a timeline, it definitely makes
sense to wait for the cleanup to be complete.
In the meantime, I'm going to set-up Jira with statuses and
workflows. And after the cleanup is done, we can move all outstanding
issues over.
Pier
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 11 oct. 05, à 12:43, Pier Fumagalli a écrit :
> Ok, there we go, here's the vote...
>
> [ ] +1 Yes please, let's move all our bugs to Jira...
+1 BUT - I'm going to start a vote about
http://wiki.apache.org/cocoon/BugzillaIssuesCleanup, to do a big
cleanup in the next two weeks, so it would be better to wait until this
is done.
I expect to start the vote tonight or tomorrow morning when I find
time, and start the cleanup process monday by changing the state of
issues, which will send mails to bug owners and reporters.
What do you think? If it's ok for you to do it after the cleanup, I'll
add this info in the cleanup message ("we're moving to jira and would
like to cleanup our issues list before"), and ping you when we're done
with the cleanup.
Also, will there be a simple mapping of old to new issues numbers after
the move? Ideally, keeping the same issue numbers in jira that we have
in bugzilla?
-Bertrand
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Ugo Cei <ug...@apache.org>.
Il giorno 11/ott/05, alle ore 12:43, Pier Fumagalli ha scritto:
> [X] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
Ugo
--
Ugo Cei
Tech Blog: http://agylen.com/
Open Source Zone: http://oszone.org/
Wine & Food Blog: http://www.divinocibo.it/
Re: [VOTE] Move to Jira (Was: Re: Jira or Bugzilla...)
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
>
> [ ] +1 Yes please, let's move all our bugs to Jira and set it up
> to work in the following way:
+0.5 :-)
My take on parts:
> Cocoon "Part":
> - Java Classes
> - Generic Components
> - Sitemap Components
> - Documentation
> - Build Environment
> - Configuration Files
> - Sitemaps
> - Flow (Flowscript, Javaflow, ...)
> - XML Files (Forms, Templates, XSP ...)
First 5 are easy ones; but not so sure about last four... Sitemaps and Configs
could be one part...
Vadim