You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by Martin Sebor <se...@roguewave.com> on 2008/02/07 23:32:24 UTC
[Fwd: JIRA now hooked up to Fisheye]
FYI: This looks quite interesting. We might want to look into
getting our svn set up with FishEye as well. What do y'all
think?
-------- Original Message --------
Subject: JIRA now hooked up to Fisheye
Date: Thu, 7 Feb 2008 18:35:06 +1100
From: Jeff Turner <je...@apache.org>
To: infrastructure@apache.org
Since JIRA 3.12+ comes bundled with the Fisheye plugin, I thought we
might as
well use it. There's now a Fisheye project tab with pretty graphs and
things,
eg:
https://issues.apache.org/jira/browse/GERONIMO?report=com.atlassian.jira.plugin.system.project:openissues-panel
and issues have a Fisheye tab if a commit was made against them.
It's enabled for the following projects, which are indexed on
fisheye6.cenqua.com:
WICKET
ODE
IBATIS
OFBIZ
GERONIMO
OPENEJB
OPENJPA
TUSCANY
This doesn't add any load to JIRA - just does HTTP GETs to the fisheye
server.
--Jeff
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by Martin Sebor <se...@roguewave.com>.
Mark Brown wrote:
> On 2/21/08, Martin Sebor <se...@roguewave.com> wrote:
>> Eric Lemings wrote:
>> >
>> > I was just touring the Crucible tool, an extension to Fisheye. It
>> > certainly appears more intuitive, easier to navigate, than certain
>> > other code review tools I've seen lately. :)
>> >
>> > http://www.atlassian.com/software/crucible/
>>
>>
>> I haven't explored Crucible much but from the little I've seen it
>> does look pretty nifty (like all the other tools from Atlassian).
>> I've been meaning to find out if they plan to open it up for Open
>> Source projects like they did with FishEye, and if so, if they
>> could set us up. I know Travis is just itching to get his hands
>> on another new tool ;-)
>
> I haven't extensive experience with code review tools but a
> common complaint I've heard from people who have used
> code review software for some time is that the discussions
> that normally take place in email can be harder to find when
> using the software.
That's also my concern. Even if the tool provides good searching
capabilities, it splinters the record of code review (and other
such) discussions into two places: email and the code review
database. That inevitably makes it more difficult to get
a complete and reliable picture of the decisions made during
the review and code changes in general.
>
> I'm also not sure that a by-invitation-only code review process
> is entirely appropriate for an open source project where you
> want to involve as many people as you can, not just the select
> few that you happen to invite as reviewers.
I admit I hadn't thought of this aspect.
I'm mostly just curious about how well Crucible works since I have
been quite impressed with all other Atlassian software, and if it's
any better than Code Collaborator, the tool some teams use at work.
Some of us find it harder to work with than just doing code reviews
the old fashioned way, in email, which may be a weakness of the tool,
or it may be that we're just behind the times ;-)
Martin
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by Mark Brown <ma...@gmail.com>.
On 2/21/08, Martin Sebor <se...@roguewave.com> wrote:
> Eric Lemings wrote:
> >
> > I was just touring the Crucible tool, an extension to Fisheye. It
> > certainly appears more intuitive, easier to navigate, than certain
> > other code review tools I've seen lately. :)
> >
> > http://www.atlassian.com/software/crucible/
>
>
> I haven't explored Crucible much but from the little I've seen it
> does look pretty nifty (like all the other tools from Atlassian).
> I've been meaning to find out if they plan to open it up for Open
> Source projects like they did with FishEye, and if so, if they
> could set us up. I know Travis is just itching to get his hands
> on another new tool ;-)
I haven't extensive experience with code review tools but a
common complaint I've heard from people who have used
code review software for some time is that the discussions
that normally take place in email can be harder to find when
using the software.
I'm also not sure that a by-invitation-only code review process
is entirely appropriate for an open source project where you
want to involve as many people as you can, not just the select
few that you happen to invite as reviewers.
-- Mark
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by Martin Sebor <se...@roguewave.com>.
Eric Lemings wrote:
>
> I was just touring the Crucible tool, an extension to Fisheye. It
> certainly appears more intuitive, easier to navigate, than certain
> other code review tools I've seen lately. :)
>
> http://www.atlassian.com/software/crucible/
I haven't explored Crucible much but from the little I've seen it
does look pretty nifty (like all the other tools from Atlassian).
I've been meaning to find out if they plan to open it up for Open
Source projects like they did with FishEye, and if so, if they
could set us up. I know Travis is just itching to get his hands
on another new tool ;-)
Martin
>
> Brad.
>
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com]
>> Sent: Saturday, February 16, 2008 2:08 PM
>> To: dev@stdcxx.apache.org
>> Subject: Re: [Fwd: JIRA now hooked up to Fisheye]
>>
>>
>> The repository has been indexed. Check it out here:
>> http://fisheye6.cenqua.com/browse/stdcxx
>>
>> Don't forget to browse to docs:
>> http://www.atlassian.com/software/fisheye/features/
>>
>>
>> Martin Sebor wrote:
>>> FYI:
>>>
>>> I opened https://support.atlassian.com/browse/FSH-520 and got our
>>> INFRA's approval to get our Subversion repository indexed at
>>> http://fisheye6.cenqua.com/ as a demo of the feature to
>> help us decide
>>> if we want to integrate it into Jira or not. The indexing
>> takes place over
>>> the weekend so if all goes according to plan the demo should be up
>>> next week.
>>>
>>>
>>> Martin Sebor wrote:
>>>> Travis Vitek wrote:
>>>>>
>>>>> Is it necessary or useful? Does it do anything to reduce
>> our workload,
>>>>> add to it, or is it totally transparent to those who
>> don't use it? What
>>>>> are the administration costs?
>>>> I thought you liked new toys ;-)
>>>>
>>>> I don't think it's necessary. The ViewVC interface to Subversion
>>>> provides similar views (without the statistics). We can get some
>>>> of the same statistics (activity per author) from Ohloh, just not
>>>> entirely up to date. The activity per issue is unique to FishEye,
>>>> AFAICS. But I don't see the statistics as essential at all.
>>>>
>>>> I do think FishEye could be useful. It shows the recent commit
>>>> history of the project, complete with ChangeLog entries for each
>>>> commit, all under the same interface as a project's issues. I.e.,
>>>> it makes it more convenient to view both issues and the changes
>>>> made to resolve them. All this data is already available, but we
>>>> have to work a little harder to get at it. For example, I use
>>>> the commits list for code review, Jira to look at issue the
>>>> changes resolve, and the issues list to monitor issue activity
>>>> in general. It looks to me as though I might be able to replace
>>>> the first two out of the three by just monitoring the FishEye
>>>> Recent Changesets view. You should check it out when you have
>>>> a few minutes:
>>>>
>>>> http://tinyurl.com/yo8jtq
>>>>
>>>> Other than figuring out who to ask to set it up for us there's
>>>> no more admin cost to us than there is to administer any other
>>>> Jira plugin we use (and there are dozens).
>>>>
>>>> Martin
>>>>
>>>>> My concern is that the stdcxx project is becoming more
>> complex to use
>>>>> and maintain. I could spend weeks trying to learn how to
>> use all of the
>>>>> software that we're currently using [subversion, jira,
>> subversion, wiki,
>>>>> forrest, ...] and I am expected to at least have some
>> knowledge of how
>>>>> to use it. Every time I sit down to use one of the tools, I end up
>>>>> spending precious time trying to figure out how to make
>> it do what I
>>>>> want it to.
>>>>>
>>>>> I see that it makes it easy to see diffs of files and file history
>>>>> without having to use the svn client or web browser. I
>> guess this could
>>>>> be useful to some, but I'm perfectly happy using the
>> existing tools for
>>>>> this.
>>>>>
>>>>> Travis
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Martin Sebor
>>>>>>
>>>>>> FYI: This looks quite interesting. We might want to look into
>>>>>> getting our svn set up with FishEye as well. What do y'all
>>>>>> think?
>>>>>>
>>>>>> -------- Original Message --------
>>>>>> From: Jeff Turner
>>>>>>
>>>>>> Since JIRA 3.12+ comes bundled with the Fisheye plugin,
>> I thought we
>>>>>> might as well use it. There's now a Fisheye project tab
>> with pretty
>>>>>> graphs and things,
>>>>>> eg:
>>>>>>
>>>>>>
>> https://issues.apache.org/jira/browse/GERONIMO?report=com.atla
>> ssian.jir
>>>>> a.plugin.system.project:openissues-panel
>>>>>> and issues have a Fisheye tab if a commit was made against them.
>>>>>>
>>>>>> It's enabled for the following projects, which are indexed on
>>>>>> fisheye6.cenqua.com:
>>>>>>
>>>>
>>>>
>>>
>> --
>> View this message in context:
>> http://www.nabble.com/-Fwd%3A-JIRA-now-hooked-up-to-Fisheye--t
>> p15345180p15518667.html
>> Sent from the stdcxx-dev mailing list archive at Nabble.com.
>>
>>
>
RE: [Fwd: JIRA now hooked up to Fisheye]
Posted by Eric Lemings <Er...@roguewave.com>.
I was just touring the Crucible tool, an extension to Fisheye. It
certainly appears more intuitive, easier to navigate, than certain
other code review tools I've seen lately. :)
http://www.atlassian.com/software/crucible/
Brad.
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]
> Sent: Saturday, February 16, 2008 2:08 PM
> To: dev@stdcxx.apache.org
> Subject: Re: [Fwd: JIRA now hooked up to Fisheye]
>
>
> The repository has been indexed. Check it out here:
> http://fisheye6.cenqua.com/browse/stdcxx
>
> Don't forget to browse to docs:
> http://www.atlassian.com/software/fisheye/features/
>
>
> Martin Sebor wrote:
> >
> > FYI:
> >
> > I opened https://support.atlassian.com/browse/FSH-520 and got our
> > INFRA's approval to get our Subversion repository indexed at
> > http://fisheye6.cenqua.com/ as a demo of the feature to
> help us decide
> > if we want to integrate it into Jira or not. The indexing
> takes place over
> > the weekend so if all goes according to plan the demo should be up
> > next week.
> >
> >
> > Martin Sebor wrote:
> >>
> >> Travis Vitek wrote:
> >>>
> >>> Is it necessary or useful? Does it do anything to reduce
> our workload,
> >>> add to it, or is it totally transparent to those who
> don't use it? What
> >>> are the administration costs?
> >>
> >> I thought you liked new toys ;-)
> >>
> >> I don't think it's necessary. The ViewVC interface to Subversion
> >> provides similar views (without the statistics). We can get some
> >> of the same statistics (activity per author) from Ohloh, just not
> >> entirely up to date. The activity per issue is unique to FishEye,
> >> AFAICS. But I don't see the statistics as essential at all.
> >>
> >> I do think FishEye could be useful. It shows the recent commit
> >> history of the project, complete with ChangeLog entries for each
> >> commit, all under the same interface as a project's issues. I.e.,
> >> it makes it more convenient to view both issues and the changes
> >> made to resolve them. All this data is already available, but we
> >> have to work a little harder to get at it. For example, I use
> >> the commits list for code review, Jira to look at issue the
> >> changes resolve, and the issues list to monitor issue activity
> >> in general. It looks to me as though I might be able to replace
> >> the first two out of the three by just monitoring the FishEye
> >> Recent Changesets view. You should check it out when you have
> >> a few minutes:
> >>
> >> http://tinyurl.com/yo8jtq
> >>
> >> Other than figuring out who to ask to set it up for us there's
> >> no more admin cost to us than there is to administer any other
> >> Jira plugin we use (and there are dozens).
> >>
> >> Martin
> >>
> >>>
> >>> My concern is that the stdcxx project is becoming more
> complex to use
> >>> and maintain. I could spend weeks trying to learn how to
> use all of the
> >>> software that we're currently using [subversion, jira,
> subversion, wiki,
> >>> forrest, ...] and I am expected to at least have some
> knowledge of how
> >>> to use it. Every time I sit down to use one of the tools, I end up
> >>> spending precious time trying to figure out how to make
> it do what I
> >>> want it to.
> >>>
> >>> I see that it makes it easy to see diffs of files and file history
> >>> without having to use the svn client or web browser. I
> guess this could
> >>> be useful to some, but I'm perfectly happy using the
> existing tools for
> >>> this.
> >>>
> >>> Travis
> >>>
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Martin Sebor
> >>>>
> >>>> FYI: This looks quite interesting. We might want to look into
> >>>> getting our svn set up with FishEye as well. What do y'all
> >>>> think?
> >>>>
> >>>> -------- Original Message --------
> >>>> From: Jeff Turner
> >>>>
> >>>> Since JIRA 3.12+ comes bundled with the Fisheye plugin,
> I thought we
> >>>> might as well use it. There's now a Fisheye project tab
> with pretty
> >>>> graphs and things,
> >>>> eg:
> >>>>
> >>>>
> https://issues.apache.org/jira/browse/GERONIMO?report=com.atla
> ssian.jir
> >>> a.plugin.system.project:openissues-panel
> >>>> and issues have a Fisheye tab if a commit was made against them.
> >>>>
> >>>> It's enabled for the following projects, which are indexed on
> >>>> fisheye6.cenqua.com:
> >>>>
> >>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/-Fwd%3A-JIRA-now-hooked-up-to-Fisheye--t
> p15345180p15518667.html
> Sent from the stdcxx-dev mailing list archive at Nabble.com.
>
>
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by Martin Sebor <se...@roguewave.com>.
The repository has been indexed. Check it out here:
http://fisheye6.cenqua.com/browse/stdcxx
Don't forget to browse to docs:
http://www.atlassian.com/software/fisheye/features/
Martin Sebor wrote:
>
> FYI:
>
> I opened https://support.atlassian.com/browse/FSH-520 and got our
> INFRA's approval to get our Subversion repository indexed at
> http://fisheye6.cenqua.com/ as a demo of the feature to help us decide
> if we want to integrate it into Jira or not. The indexing takes place over
> the weekend so if all goes according to plan the demo should be up
> next week.
>
>
> Martin Sebor wrote:
>>
>> Travis Vitek wrote:
>>>
>>> Is it necessary or useful? Does it do anything to reduce our workload,
>>> add to it, or is it totally transparent to those who don't use it? What
>>> are the administration costs?
>>
>> I thought you liked new toys ;-)
>>
>> I don't think it's necessary. The ViewVC interface to Subversion
>> provides similar views (without the statistics). We can get some
>> of the same statistics (activity per author) from Ohloh, just not
>> entirely up to date. The activity per issue is unique to FishEye,
>> AFAICS. But I don't see the statistics as essential at all.
>>
>> I do think FishEye could be useful. It shows the recent commit
>> history of the project, complete with ChangeLog entries for each
>> commit, all under the same interface as a project's issues. I.e.,
>> it makes it more convenient to view both issues and the changes
>> made to resolve them. All this data is already available, but we
>> have to work a little harder to get at it. For example, I use
>> the commits list for code review, Jira to look at issue the
>> changes resolve, and the issues list to monitor issue activity
>> in general. It looks to me as though I might be able to replace
>> the first two out of the three by just monitoring the FishEye
>> Recent Changesets view. You should check it out when you have
>> a few minutes:
>>
>> http://tinyurl.com/yo8jtq
>>
>> Other than figuring out who to ask to set it up for us there's
>> no more admin cost to us than there is to administer any other
>> Jira plugin we use (and there are dozens).
>>
>> Martin
>>
>>>
>>> My concern is that the stdcxx project is becoming more complex to use
>>> and maintain. I could spend weeks trying to learn how to use all of the
>>> software that we're currently using [subversion, jira, subversion, wiki,
>>> forrest, ...] and I am expected to at least have some knowledge of how
>>> to use it. Every time I sit down to use one of the tools, I end up
>>> spending precious time trying to figure out how to make it do what I
>>> want it to.
>>>
>>> I see that it makes it easy to see diffs of files and file history
>>> without having to use the svn client or web browser. I guess this could
>>> be useful to some, but I'm perfectly happy using the existing tools for
>>> this.
>>>
>>> Travis
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Martin Sebor
>>>>
>>>> FYI: This looks quite interesting. We might want to look into
>>>> getting our svn set up with FishEye as well. What do y'all
>>>> think?
>>>>
>>>> -------- Original Message --------
>>>> From: Jeff Turner
>>>>
>>>> Since JIRA 3.12+ comes bundled with the Fisheye plugin, I thought we
>>>> might as well use it. There's now a Fisheye project tab with pretty
>>>> graphs and things,
>>>> eg:
>>>>
>>>> https://issues.apache.org/jira/browse/GERONIMO?report=com.atlassian.jir
>>> a.plugin.system.project:openissues-panel
>>>> and issues have a Fisheye tab if a commit was made against them.
>>>>
>>>> It's enabled for the following projects, which are indexed on
>>>> fisheye6.cenqua.com:
>>>>
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/-Fwd%3A-JIRA-now-hooked-up-to-Fisheye--tp15345180p15518667.html
Sent from the stdcxx-dev mailing list archive at Nabble.com.
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by Martin Sebor <se...@roguewave.com>.
FYI:
I opened https://support.atlassian.com/browse/FSH-520 and got our
INFRA's approval to get our Subversion repository indexed at
http://fisheye6.cenqua.com/ as a demo of the feature to help us decide
if we want to integrate it into Jira or not. The indexing takes place over
the weekend so if all goes according to plan the demo should be up
next week.
Martin Sebor wrote:
>
> Travis Vitek wrote:
>>
>> Is it necessary or useful? Does it do anything to reduce our workload,
>> add to it, or is it totally transparent to those who don't use it? What
>> are the administration costs?
>
> I thought you liked new toys ;-)
>
> I don't think it's necessary. The ViewVC interface to Subversion
> provides similar views (without the statistics). We can get some
> of the same statistics (activity per author) from Ohloh, just not
> entirely up to date. The activity per issue is unique to FishEye,
> AFAICS. But I don't see the statistics as essential at all.
>
> I do think FishEye could be useful. It shows the recent commit
> history of the project, complete with ChangeLog entries for each
> commit, all under the same interface as a project's issues. I.e.,
> it makes it more convenient to view both issues and the changes
> made to resolve them. All this data is already available, but we
> have to work a little harder to get at it. For example, I use
> the commits list for code review, Jira to look at issue the
> changes resolve, and the issues list to monitor issue activity
> in general. It looks to me as though I might be able to replace
> the first two out of the three by just monitoring the FishEye
> Recent Changesets view. You should check it out when you have
> a few minutes:
>
> http://tinyurl.com/yo8jtq
>
> Other than figuring out who to ask to set it up for us there's
> no more admin cost to us than there is to administer any other
> Jira plugin we use (and there are dozens).
>
> Martin
>
>>
>> My concern is that the stdcxx project is becoming more complex to use
>> and maintain. I could spend weeks trying to learn how to use all of the
>> software that we're currently using [subversion, jira, subversion, wiki,
>> forrest, ...] and I am expected to at least have some knowledge of how
>> to use it. Every time I sit down to use one of the tools, I end up
>> spending precious time trying to figure out how to make it do what I
>> want it to.
>>
>> I see that it makes it easy to see diffs of files and file history
>> without having to use the svn client or web browser. I guess this could
>> be useful to some, but I'm perfectly happy using the existing tools for
>> this.
>>
>> Travis
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Martin Sebor
>>>
>>> FYI: This looks quite interesting. We might want to look into
>>> getting our svn set up with FishEye as well. What do y'all
>>> think?
>>>
>>> -------- Original Message --------
>>> From: Jeff Turner
>>>
>>> Since JIRA 3.12+ comes bundled with the Fisheye plugin, I thought we
>>> might as well use it. There's now a Fisheye project tab with pretty
>>> graphs and things,
>>> eg:
>>>
>>> https://issues.apache.org/jira/browse/GERONIMO?report=com.atlassian.jir
>> a.plugin.system.project:openissues-panel
>>> and issues have a Fisheye tab if a commit was made against them.
>>>
>>> It's enabled for the following projects, which are indexed on
>>> fisheye6.cenqua.com:
>>>
>
>
>
--
View this message in context: http://www.nabble.com/-Fwd%3A-JIRA-now-hooked-up-to-Fisheye--tp15345180p15420336.html
Sent from the stdcxx-dev mailing list archive at Nabble.com.
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by Martin Sebor <se...@roguewave.com>.
Travis Vitek wrote:
>
> Is it necessary or useful? Does it do anything to reduce our workload,
> add to it, or is it totally transparent to those who don't use it? What
> are the administration costs?
I thought you liked new toys ;-)
I don't think it's necessary. The ViewVC interface to Subversion
provides similar views (without the statistics). We can get some
of the same statistics (activity per author) from Ohloh, just not
entirely up to date. The activity per issue is unique to FishEye,
AFAICS. But I don't see the statistics as essential at all.
I do think FishEye could be useful. It shows the recent commit
history of the project, complete with ChangeLog entries for each
commit, all under the same interface as a project's issues. I.e.,
it makes it more convenient to view both issues and the changes
made to resolve them. All this data is already available, but we
have to work a little harder to get at it. For example, I use
the commits list for code review, Jira to look at issue the
changes resolve, and the issues list to monitor issue activity
in general. It looks to me as though I might be able to replace
the first two out of the three by just monitoring the FishEye
Recent Changesets view. You should check it out when you have
a few minutes:
http://tinyurl.com/yo8jtq
Other than figuring out who to ask to set it up for us there's
no more admin cost to us than there is to administer any other
Jira plugin we use (and there are dozens).
Martin
>
> My concern is that the stdcxx project is becoming more complex to use
> and maintain. I could spend weeks trying to learn how to use all of the
> software that we're currently using [subversion, jira, subversion, wiki,
> forrest, ...] and I am expected to at least have some knowledge of how
> to use it. Every time I sit down to use one of the tools, I end up
> spending precious time trying to figure out how to make it do what I
> want it to.
>
> I see that it makes it easy to see diffs of files and file history
> without having to use the svn client or web browser. I guess this could
> be useful to some, but I'm perfectly happy using the existing tools for
> this.
>
> Travis
>
>
>
>
>> -----Original Message-----
>> From: Martin Sebor
>>
>> FYI: This looks quite interesting. We might want to look into
>> getting our svn set up with FishEye as well. What do y'all
>> think?
>>
>> -------- Original Message --------
>> From: Jeff Turner
>>
>> Since JIRA 3.12+ comes bundled with the Fisheye plugin, I thought we
>> might as well use it. There's now a Fisheye project tab with pretty
>> graphs and things,
>> eg:
>>
>> https://issues.apache.org/jira/browse/GERONIMO?report=com.atlassian.jir
> a.plugin.system.project:openissues-panel
>> and issues have a Fisheye tab if a commit was made against them.
>>
>> It's enabled for the following projects, which are indexed on
>> fisheye6.cenqua.com:
>>
Re: [Fwd: JIRA now hooked up to Fisheye]
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Travis Vitek wrote:
>
> Is it necessary or useful? Does it do anything to reduce our workload,
> add to it, or is it totally transparent to those who don't use it? What
> are the administration costs?
as far as I understand, CIA.vc, fisheye etc all are interesting ways to
peer into svn or announce its results. But none of these sorts of tools
add headaches to the typical participant in a project.
RE: [Fwd: JIRA now hooked up to Fisheye]
Posted by Travis Vitek <Tr...@roguewave.com>.
Is it necessary or useful? Does it do anything to reduce our workload,
add to it, or is it totally transparent to those who don't use it? What
are the administration costs?
My concern is that the stdcxx project is becoming more complex to use
and maintain. I could spend weeks trying to learn how to use all of the
software that we're currently using [subversion, jira, subversion, wiki,
forrest, ...] and I am expected to at least have some knowledge of how
to use it. Every time I sit down to use one of the tools, I end up
spending precious time trying to figure out how to make it do what I
want it to.
I see that it makes it easy to see diffs of files and file history
without having to use the svn client or web browser. I guess this could
be useful to some, but I'm perfectly happy using the existing tools for
this.
Travis
>-----Original Message-----
>From: Martin Sebor
>
>FYI: This looks quite interesting. We might want to look into
>getting our svn set up with FishEye as well. What do y'all
>think?
>
>-------- Original Message --------
>From: Jeff Turner
>
>Since JIRA 3.12+ comes bundled with the Fisheye plugin, I thought we
>might as well use it. There's now a Fisheye project tab with pretty
>graphs and things,
>eg:
>
>https://issues.apache.org/jira/browse/GERONIMO?report=com.atlassian.jir
a.plugin.system.project:openissues-panel
>
>and issues have a Fisheye tab if a commit was made against them.
>
>It's enabled for the following projects, which are indexed on
>fisheye6.cenqua.com:
>