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" stat
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 "WO
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
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
t
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 a
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 ne
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 i
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 firs
On 10/14/05, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> Le 14 oct. 05, à 15:46, Peter Hunsberger a écrit :
>
> 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
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
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
On 10/14/05, Bertrand Delacretaz <[EMAIL PROTECTED]> 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 comp
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
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
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 tr
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 m
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
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
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 whe
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
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
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
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,
> > 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
Arjé
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
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
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
-
Pier Fumagalli 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
Pier Fumagalli wrote:
> Ok, there we go, here's the vote...
0 ... i don't care which issue tracking system we use.
-David
Gianugo Rabellino wrote:
On 10/11/05, Pier Fumagalli <[EMAIL PROTECTED]> 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
On 10/11/05, Pier Fumagalli <[EMAIL PROTECTED]> 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
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
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
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 C
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.divi
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
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/
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
- W
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
39 matches
Mail list logo