Is this the right place for questions about the Spoon code base?

I'm a new user and I think I've found a bug in the Spoon code base.
Is this the right place to discuss it?

--
Peter Hunsberger

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "kettle-developers" group.
To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to kettle-developers+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi peter,

first welcome here :-)
You can raise a bug in the Pentaho bug tracking system (after logged) :

http://jira.pentaho.com/browse/PDI?r...arissues-panel

Take care

Samatar




________________________________
De : Peter Hunsberger <peter.hunsberger (AT) gmail (DOT) com>

I opened bug PDI-2607 on the 10th. Yesterday I added another comment
on it, essentially, I think I know what the proper fix is now.
However, it seems that adding comments to an already existing bug
doesn't get much attention... I can give you the basics here, or I
can wait for a response on the bug?

On Wed, Aug 19, 2009 at 2:32 PM, samatar hassan<sahass78 (AT) yahoo (DOT) fr> wrote:[color=blue]
> Hi peter,
>
> first welcome here :-)
> You can raise a bug in the Pentaho bug tracking system (after logged) :
>
> http://jira.pentaho.com/browse/PDI?r...arissues-panel
>
> Take care
>
> Samatar
>
> ________________________________
> De : Peter Hunsberger <peter.hunsberger (AT) gmail (DOT) com>
>

Hi Peter,

thanks for reporting this bug...

....and thanks for Matt who wrote this wonderful piece of "Read me
first!" on the forum. Now, I can just copy and paste:

"What is certain is that we give our Enterprise Edition customers and
partners priority with respect to both bug resolution and feature
requests. Beyond the paying customers we look at the popularity of
certain bugs, the votes they get, etc."

Nevertheless thanks again for reporting and looking into this!

Cheers,
Jens


Peter Hunsberger schrieb:[color=blue]
> I opened bug PDI-2607 on the 10th. Yesterday I added another comment
> on it, essentially, I think I know what the proper fix is now.
> However, it seems that adding comments to an already existing bug
> doesn't get much attention... I can give you the basics here, or I
> can wait for a response on the bug?
>
> On Wed, Aug 19, 2009 at 2:32 PM, samatar hassan<sahass78 (AT) yahoo (DOT) fr> wrote:[color=green]
>> Hi peter,
>>
>> first welcome here :-)
>> You can raise a bug in the Pentaho bug tracking system (after logged) :
>>
>> http://jira.pentaho.com/browse/PDI?r...arissues-panel
>>
>> Take care
>>
>> Samatar
>>
>> ________________________________
>> De : Peter Hunsberger <peter.hunsberger (AT) gmail (DOT) com>
>>

Ok, sorry but that's a completely useless answer. This bug will hit
everyone that has to do a file load on a file with wrapped lines, even
the ones paying for support... It might also affect other use cases
(I haven't tested.) I'm offering to send you a patch here, I'd just
like an opinion on which of the two possible ways of doing the fix
would make the most sense. However, if you don't want the fix I can
continue to run my patched version.

On Thu, Aug 20, 2009 at 2:35 AM, Jens Bleuel<jbleuel (AT) pentaho (DOT) com> wrote:[color=blue]
>
> Hi Peter,
>
> thanks for reporting this bug...
>
> ...and thanks for Matt who wrote this wonderful piece of "Read me
> first!" on the forum. Now, I can just copy and paste:
>
> "What is certain is that we give our Enterprise Edition customers and
> partners priority with respect to both bug resolution and feature
> requests. Beyond the paying customers we look at the popularity of
> certain bugs, the votes they get, etc."
>
> Nevertheless thanks again for reporting and looking into this!
>
> Cheers,
> Jens
>
>
> Peter Hunsberger schrieb:[color=green]
>> I opened bug PDI-2607 on the 10th.

Hey Peter,

come on ...

My reply was on your comment about the attention to the JIRA case and
believe me, we didn't had such a case in the customer support portal, yet.

.... you are welcome to attach the fix (best against trunk and 3.2.2) to
the JIRA case.

Thanks much,
Jens



Peter Hunsberger schrieb:[color=blue]
> Ok, sorry but that's a completely useless answer. This bug will hit
> everyone that has to do a file load on a file with wrapped lines, even
> the ones paying for support... It might also affect other use cases
> (I haven't tested.) I'm offering to send you a patch here, I'd just
> like an opinion on which of the two possible ways of doing the fix
> would make the most sense. However, if you don't want the fix I can
> continue to run my patched version.
>
> On Thu, Aug 20, 2009 at 2:35 AM, Jens Bleuel<jbleuel (AT) pentaho (DOT) com> wrote:[color=green]
>> Hi Peter,
>>
>> thanks for reporting this bug...
>>
>> ...and thanks for Matt who wrote this wonderful piece of "Read me
>> first!" on the forum. Now, I can just copy and paste:
>>
>> "What is certain is that we give our Enterprise Edition customers and
>> partners priority with respect to both bug resolution and feature
>> requests. Beyond the paying customers we look at the popularity of
>> certain bugs, the votes they get, etc."
>>
>> Nevertheless thanks again for reporting and looking into this!
>>
>> Cheers,
>> Jens
>>
>>
>> Peter Hunsberger schrieb:[color=darkred]
>>> I opened bug PDI-2607 on the 10th. Yesterday I added another comment
>>> on it, essentially, I think I know what the proper fix is now.
>>> However, it seems that adding comments to an already existing bug
>>> doesn't get much attention... I can give you the basics here, or I
>>> can wait for a response on the bug?
>>>
>>> On Wed, Aug 19, 2009 at 2:32 PM, samatar hassan<sahass78 (AT) yahoo (DOT) fr> wrote:
>>>> Hi peter,
>>>>
>>>> first welcome here :-)
>>>> You can raise a bug in the Pentaho bug tracking system (after logged) :
>>>>
>>>> http://jira.pentaho.com/browse/PDI?r...arissues-panel
>>>>
>>>> Take care
>>>>
>>>> Samatar
>>>>
>>>> ________________________________
>>>> De : Peter Hunsberger <peter.hunsberger (AT) gmail (DOT) com>
>>>>

I can understand that paying customers get priority, but when you've
got someone who's willing to track down the cause of a bug and fix it
you'd hope that someone would be willing to pay attention....

As I posted originally, I have some questions about what's the best
way to do the fix. Looks like this is the best place to ask about
them so I will start a new thread here on the issue.

On Thu, Aug 20, 2009 at 9:20 AM, Jens Bleuel<jbleuel (AT) pentaho (DOT) com> wrote:[color=blue]
>
> Hey Peter,
>
> come on ...
>
> My reply was on your comment about the attention to the JIRA case and
> believe me, we didn't had such a case in the customer support portal, yet..
>
> ... you are welcome to attach the fix (best against trunk and 3.2.2) to
> the JIRA case.
>
> Thanks much,
> Jens
>
>
>
> Peter Hunsberger schrieb:[color=green]
>> Ok, sorry but that's a completely useless answer.

Hi Peter,

Thanks for looking into this. Now allow me to sound like a broken record and ask you to follow Samatar's advice : file a bug report in JIRA or look for an existing case.
Attach the patch and reproduction path (including sample xform/text file) to the JIRA case.
Then as Jens said it will go through standard triage process.

Of-course, only then the work can really start:
- evaluation of the fix
- run checks to see if all still works as before (backward compatibility tests, run unit tests)
- create an extra unit test
- etc.

Then someone can apply the fix.
If you don't like the speed at which we do this work, keep a local source tree, get a support contract or find a lonely developer with commit rights that wants to do the work above.

Let me note that after a few good patches we're usually rather quick to grant (serious) people commit access to the PDI Subversion repositories.
3 devs have joined in the last month alone.

Those are the rules of the game. If you don't like them, that's just tough luck :-)

Take care,
Matt

Matt Casters <mcasters (AT) pentaho (DOT) org>
Chief Data Integration
Fonteinstraat 70, 9400 OKEGEM - Belgium - Cell : +32 486 97 29 37
Pentaho : The Commercial Open Source Alternative for Business Intelligence



On Thursday 20 August 2009 18:12:43 Peter Hunsberger wrote:[color=blue]
>
> I can understand that paying customers get priority, but when you've
> got someone who's willing to track down the cause of a bug and fix it
> you'd hope that someone would be willing to pay attention....
>
> As I posted originally, I have some questions about what's the best
> way to do the fix. Looks like this is the best place to ask about
> them so I will start a new thread here on the issue.
>
> On Thu, Aug 20, 2009 at 9:20 AM, Jens Bleuel<jbleuel (AT) pentaho (DOT) com> wrote:[color=green]
> >
> > Hey Peter,
> >
> > come on ...
> >
> > My reply was on your comment about the attention to the JIRA case and
> > believe me, we didn't had such a case in the customer support portal, yet.
> >
> > ... you are welcome to attach the fix (best against trunk and 3.2.2) to
> > the JIRA case.
> >
> > Thanks much,
> > Jens
> >
> >
> >
> > Peter Hunsberger schrieb:[color=darkred]
> >> Ok, sorry but that's a completely useless answer. This bug will hit
> >> everyone that has to do a file load on a file with wrapped lines, even
> >> the ones paying for support... It might also affect other use cases
> >> (I haven't tested.) I'm offering to send you a patch here, I'd just
> >> like an opinion on which of the two possible ways of doing the fix
> >> would make the most sense. However, if you don't want the fix I can
> >> continue to run my patched version.
> >>
> >> On Thu, Aug 20, 2009 at 2:35 AM, Jens Bleuel<jbleuel (AT) pentaho (DOT) com> wrote:
> >>> Hi Peter,
> >>>
> >>> thanks for reporting this bug...
> >>>
> >>> ...and thanks for Matt who wrote this wonderful piece of "Read me
> >>> first!" on the forum. Now, I can just copy and paste:
> >>>
> >>> "What is certain is that we give our Enterprise Edition customers and
> >>> partners priority with respect to both bug resolution and feature
> >>> requests. Beyond the paying customers we look at the popularity of
> >>> certain bugs, the votes they get, etc."
> >>>
> >>> Nevertheless thanks again for reporting and looking into this!
> >>>
> >>> Cheers,
> >>> Jens
> >>>
> >>>
> >>> Peter Hunsberger schrieb:
> >>>> I opened bug PDI-2607 on the 10th. Yesterday I added another comment
> >>>> on it, essentially, I think I know what the proper fix is now.
> >>>> However, it seems that adding comments to an already existing bug
> >>>> doesn't get much attention... I can give you the basics here, or I
> >>>> can wait for a response on the bug?
> >>>>
> >>>> On Wed, Aug 19, 2009 at 2:32 PM, samatar hassan<sahass78 (AT) yahoo (DOT) fr> wrote:
> >>>>> Hi peter,
> >>>>>
> >>>>> first welcome here :-)
> >>>>> You can raise a bug in the Pentaho bug tracking system (after logged) :
> >>>>>
> >>>>> http://jira.pentaho.com/browse/PDI?r...arissues-panel
> >>>>>
> >>>>> Take care
> >>>>>
> >>>>> Samatar
> >>>>>
> >>>>> ________________________________
> >>>>> De : Peter Hunsberger <peter.hunsberger (AT) gmail (DOT) com>
> >>>>>

On Thu, Aug 20, 2009 at 11:27 AM, Matt Casters<mcasters (AT) pentaho (DOT) org> wrote:
>
> Hi Peter,
>
> Thanks for looking into this. Now allow me to sound like a broken record and
> ask you to follow Samatar's advice : file a bug report in JIRA or look for
> an existing case.
> Attach the patch and reproduction path (including sample xform/text file) to
> the JIRA case.
> Then as Jens said it will go through standard triage process.

Matt, if you read through this thread you'll see I already opened the
JIRA case. However, not being familiar with the code base I'm trying
to get some guidance as to which possible version of two different
fixes would make the most sense.

> Of-course, only then the work can really start:
> - evaluation of the fix
> - run checks to see if all still works as before (backward compatibility
> tests, run unit tests)
> - create an extra unit test
> - etc.
>
> Then someone can apply the fix.
> If you don't like the speed at which we do this work, keep a local source
> tree, get a support contract or find a lonely developer with commit rights
> that wants to do the work above.
>
> Let me note that after a few good patches we're usually rather quick to
> grant (serious) people commit access to the PDI Subversion repositories.
> 3 devs have joined in the last month alone.

I'm already an Apache committer, I don't really have time for another
project. :-)
[color=blue]
>
> Those are the rules of the game. If you don't like them, that's just tough
> luck :-)
>
> Take care,
> Matt
>
> Matt Casters <mcasters (AT) pentaho (DOT) org>
> Chief Data Integration
> Fonteinstraat 70, 9400 OKEGEM - Belgium - Cell : +32 486 97 29 37
> Pentaho : The Commercial Open Source Alternative for Business Intelligence
>
>
>
> On Thursday 20 August 2009 18:12:43 Peter Hunsberger wrote:[color=green]
>>
>> I can understand that paying customers get priority, but when you've
>> got someone who's willing to track down the cause of a bug and fix it
>> you'd hope that someone would be willing to pay attention....
>>
>> As I posted originally, I have some questions about what's the best
>> way to do the fix. Looks like this is the best place to ask about
>> them so I will start a new thread here on the issue.
>>
>> On Thu, Aug 20, 2009 at 9:20 AM, Jens Bleuel<jbleuel (AT) pentaho (DOT) com> wrote:[color=darkred]
>> >
>> > Hey Peter,
>> >
>> > come on ...
>> >
>> > My reply was on your comment about the attention to the JIRA case and
>> > believe me, we didn't had such a case in the customer support portal,
>> > yet.
>> >
>> > ... you are welcome to attach the fix (best against trunk and 3.2.2) to
>> > the JIRA case.
>> >
>> > Thanks much,
>> > Jens
>> >
>> >
>> >
>> > Peter Hunsberger schrieb:
>> >> Ok, sorry but that's a completely useless answer.