You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Greg Monroe <Gr...@DukeCE.com> on 2006/10/05 23:19:43 UTC
RE: Old torque bugs from scarab
> Jeff turner has imported the old bugs from Scarab into jira, they can be
> found in
>
> http://issues.apache.org/jira/browse/TORQUEOLD <http://issues.apache.org/jira/browse/TORQUEOLD>
>
> The question si now whether they should be left under a separate key, or
> whether the issues should be bulk moved to the current Torque project.
...
>
> My personal impression is that many things are still relevant to Torque,
> but most are "things which should be hcanged" and not many explicit bugs.
> So I'm still divided whether we should keep the old issues separate or
> not. Any opinions ?
I noticed that you can vote on the issues. Could this be used as an
easy way to filter the good from the not so good stuff? Move popular
items over?
> P.S. I'm away on vacation next week. I'lll look though the remaining
> issues when I'm back.
Slackard... I'm on vacation this week too and I've responded JOKE!,
had some work commitments this PM that caused me to read my mail..
and get sucked into Torque stuff.
Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.
RE: Old torque bugs from scarab
Posted by Thomas Fischer <tf...@apache.org>.
On Thu, 5 Oct 2006, Greg Monroe wrote:
> FWIW, did a quick look thru the open issues and saw 3 that were either
> duplicated or superceeded by Torque-### issues. So, I added links to
> the new issues. Here's a link to see them:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310542&updated%3Aafter=4%2FOct%2F06&sorter/field=issuekey&sorter/order=DESC <https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310542&updated%3Aafter=4%2FOct%2F06&sorter/field=issuekey&sorter/order=DESC>
>
Thanks a lot, I have marked them as resolved->Duplicate
> Is Scarab no longer available? I wanted to see the extra info there
> but could not get into it.
>
Scarab was shut down because the resources on the machine were it ran on
were needed by the other issue trackers. I do not know where the extra
information is available.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
RE: Old torque bugs from scarab
Posted by Greg Monroe <Gr...@DukeCE.com>.
FWIW, did a quick look thru the open issues and saw 3 that were either
duplicated or superceeded by Torque-### issues. So, I added links to
the new issues. Here's a link to see them:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310542&updated%3Aafter=4%2FOct%2F06&sorter/field=issuekey&sorter/order=DESC <https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310542&updated%3Aafter=4%2FOct%2F06&sorter/field=issuekey&sorter/order=DESC>
Is Scarab no longer available? I wanted to see the extra info there
but could not get into it.
Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.