Error generating PDF invoice

[Jacques Le Roux]

Hey Scott, that's right!

Happy to close this one. So eventually you were right, there are ANY blocking bugs in OFBiz under our criteria ;o)

Though I guess we should better define our criteria for blocking. Because if we allow to use blocking only for bugs blocking all
OFBiz there should be hardly any such bugs. I mean it would be very, very quickly fixed and we would have hardly the time to create
a blocking bug. Notbaly because we have now BuildBot running and all commiters are quickly aware of any errors they woulds have
made. Did you thought about it Scott, what is your perception?

Thanks

Jacques

Scott Gray wrote:

> Hi Jacques,
>
> I thought you fixed OFBIZ-3837 recently?  Or was that some other shipping estimate problem you were working on?
>
> Regards
> Scott
>
> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>
>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 are reopened.
>> This is againt all versions. There are only 78 for trunk but this is not a reliable criteria (if any are)
>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. But I guess not under Scott's criteria (it's not
>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 are critical and 173 major
>>
>> No needs to say that any help to clean things would be really appreciated...
>>
>> HTH
>>
>> Jacques
>>
>> From: "BJ Freeman" <[hidden email]>
>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>
>>> =========================
>>> BJ Freeman  <http://bjfreeman.elance.com>
>>> Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>> Specialtymarket.com  <http://www.specialtymarket.com/>
>>> Systems Integrator-- Glad to Assist
>>>
>>> Chat  Y! messenger: bjfr33man
>>>
>>>
>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>> Actually I meant a response to it like there are no bugs that fit this
>>>> condition.
>>>>
>>>> =========================
>>>> BJ Freeman <http://bjfreeman.elance.com>
>>>> Strategic Power Office with Supplier Automation
>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>> Specialtymarket.com <http://www.specialtymarket.com/>
>>>> Systems Integrator-- Glad to Assist
>>>>
>>>> Chat Y! messenger: bjfr33man
>>>>
>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>
>>>>
>>>>> You missed something by reading an email from a community member and
>>>>> interpreting it's contents as some sort of official policy.
>>>>>
>>>>> Regards
>>>>> Scott
>>>>>
>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>
>>>>>> I was reffering to this:
>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>> I guess the basic questions might be: Did we have an official "freeze"
>>>>>>> process where we only accepted bug fixes against that branch? Do we
>>>>>>> have
>>>>>>> any open bugs that are considered "release critical"?
>>>>>>
>>>>>> I agree. At least *all* bugs should be looked at, and given a target
>>>>>> release tag, etc. Time for some bug triage. I don't think there has
>>>>>> been a concerted effort like that in like, forever.
>>>>>>
>>>>>>
>>>>>> I have not seen anything that shows this as taken care of.
>>>>>> Have I missed something?
>>>>>>
>>>>>> =========================
>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>> Strategic Power Office with Supplier
>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>
>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>> Systems Integrator-- Glad to Assist
>>>>>>
>>>>>> Chat Y! messenger: bjfr33man
>>>>>>
>>>>>>
>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>
>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>
>>>>>>>> There are a number of bugs that have to be resolved before release
>>>>>>>> remember this is a volunteer effort so there is no full time person
>>>>>>>> doing the patches for the bugs.
>>>>>>>
>>>>>>> What are you basing this on?
>>>>>>>
>>>>>>>> once they are completed and testing has been done then there will
>>>>>>>> be a release.
>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>
>>>>>>> What are you basing this on? Maybe there is some confusion... the
>>>>>>> date on a release is the date it was branched from the trunk, not
>>>>>>> the date that a binary release is done from the branch.
>>>>>>>
>>>>>>> -David
>>>>>>>
>>>>>>>
>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release date?
>>>>>>>>> Just curious.

[Scott Gray-2]

A blocking bug IMO is nothing more than the community (rather than an individual) deciding that a bug is important enough that a release shouldn't occur until it is fixed.  I don't think we need any criteria other than that really.

Regards
Scott

On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:

> Hey Scott, that's right!
>
> Happy to close this one. So eventually you were right, there are ANY blocking bugs in OFBiz under our criteria ;o)
>
> Though I guess we should better define our criteria for blocking. Because if we allow to use blocking only for bugs blocking all OFBiz there should be hardly any such bugs. I mean it would be very, very quickly fixed and we would have hardly the time to create a blocking bug. Notbaly because we have now BuildBot running and all commiters are quickly aware of any errors they woulds have made. Did you thought about it Scott, what is your perception?
>
> Thanks
>
> Jacques
>
> Scott Gray wrote:
>> Hi Jacques,
>>
>> I thought you fixed OFBIZ-3837 recently?  Or was that some other shipping estimate problem you were working on?
>>
>> Regards
>> Scott
>>
>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>
>>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 are reopened.
>>> This is againt all versions. There are only 78 for trunk but this is not a reliable criteria (if any are)
>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. But I guess not under Scott's criteria (it's not
>>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 are critical and 173 major
>>>
>>> No needs to say that any help to clean things would be really appreciated...
>>>
>>> HTH
>>>
>>> Jacques
>>>
>>> From: "BJ Freeman" <[hidden email]>
>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>
>>>> =========================
>>>> BJ Freeman  <http://bjfreeman.elance.com>
>>>> Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>> Specialtymarket.com  <http://www.specialtymarket.com/>
>>>> Systems Integrator-- Glad to Assist
>>>>
>>>> Chat  Y! messenger: bjfr33man
>>>>
>>>>
>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>> Actually I meant a response to it like there are no bugs that fit this
>>>>> condition.
>>>>>
>>>>> =========================
>>>>> BJ Freeman <http://bjfreeman.elance.com>
>>>>> Strategic Power Office with Supplier Automation
>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>> Specialtymarket.com <http://www.specialtymarket.com/>
>>>>> Systems Integrator-- Glad to Assist
>>>>>
>>>>> Chat Y! messenger: bjfr33man
>>>>>
>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>
>>>>>
>>>>>> You missed something by reading an email from a community member and
>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>
>>>>>> Regards
>>>>>> Scott
>>>>>>
>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>
>>>>>>> I was reffering to this:
>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>> I guess the basic questions might be: Did we have an official "freeze"
>>>>>>>> process where we only accepted bug fixes against that branch? Do we
>>>>>>>> have
>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>
>>>>>>> I agree. At least *all* bugs should be looked at, and given a target
>>>>>>> release tag, etc. Time for some bug triage. I don't think there has
>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>
>>>>>>>
>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>> Have I missed something?
>>>>>>>
>>>>>>> =========================
>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>> Strategic Power Office with Supplier
>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>
>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>
>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>
>>>>>>>
>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>
>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>
>>>>>>>>> There are a number of bugs that have to be resolved before release
>>>>>>>>> remember this is a volunteer effort so there is no full time person
>>>>>>>>> doing the patches for the bugs.
>>>>>>>>
>>>>>>>> What are you basing this on?
>>>>>>>>
>>>>>>>>> once they are completed and testing has been done then there will
>>>>>>>>> be a release.
>>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>>
>>>>>>>> What are you basing this on? Maybe there is some confusion... the
>>>>>>>> date on a release is the date it was branched from the trunk, not
>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>
>>>>>>>> -David
>>>>>>>>
>>>>>>>>
>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release date?
>>>>>>>>>> Just curious.
>
>

[Jacques Le Roux]

Scott Gray wrote:
> A blocking bug IMO is nothing more than the community (rather than an individual) deciding that a bug is important enough that a
> release shouldn't occur until it is fixed.  I don't think we need any criteria other than that really.

Yes that's fine to me. And a critical (for instance at https://issues.apache.org/jira/browse/OFBIZ-3912)?

Jacques
 

> Regards
> Scott
>
> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>
>> Hey Scott, that's right!
>>
>> Happy to close this one. So eventually you were right, there are ANY blocking bugs in OFBiz under our criteria ;o)
>>
>> Though I guess we should better define our criteria for blocking. Because if we allow to use blocking only for bugs blocking all
>> OFBiz there should be hardly any such bugs. I mean it would be very, very quickly fixed and we would have hardly the time to
>> create a blocking bug. Notbaly because we have now BuildBot running and all commiters are quickly aware of any errors they
>> woulds have made. Did you thought about it Scott, what is your perception?  
>>
>> Thanks
>>
>> Jacques
>>
>> Scott Gray wrote:
>>> Hi Jacques,
>>>
>>> I thought you fixed OFBIZ-3837 recently?  Or was that some other shipping estimate problem you were working on?
>>>
>>> Regards
>>> Scott
>>>
>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>
>>>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 are reopened.
>>>> This is againt all versions. There are only 78 for trunk but this is not a reliable criteria (if any are)
>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. But I guess not under Scott's criteria (it's not
>>>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 are critical and 173 major
>>>>
>>>> No needs to say that any help to clean things would be really appreciated...
>>>>
>>>> HTH
>>>>
>>>> Jacques
>>>>
>>>> From: "BJ Freeman" <[hidden email]>
>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>
>>>>> =========================
>>>>> BJ Freeman  <http://bjfreeman.elance.com>
>>>>> Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>> Specialtymarket.com  <http://www.specialtymarket.com/>
>>>>> Systems Integrator-- Glad to Assist
>>>>>
>>>>> Chat  Y! messenger: bjfr33man
>>>>>
>>>>>
>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>> Actually I meant a response to it like there are no bugs that fit this
>>>>>> condition.
>>>>>>
>>>>>> =========================
>>>>>> BJ Freeman <http://bjfreeman.elance.com>
>>>>>> Strategic Power Office with Supplier Automation
>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>> Specialtymarket.com <http://www.specialtymarket.com/>
>>>>>> Systems Integrator-- Glad to Assist
>>>>>>
>>>>>> Chat Y! messenger: bjfr33man
>>>>>>
>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>
>>>>>>
>>>>>>> You missed something by reading an email from a community member and
>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>
>>>>>>> Regards
>>>>>>> Scott
>>>>>>>
>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>
>>>>>>>> I was reffering to this:
>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>> I guess the basic questions might be: Did we have an official "freeze"
>>>>>>>>> process where we only accepted bug fixes against that branch? Do we
>>>>>>>>> have
>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>
>>>>>>>> I agree. At least *all* bugs should be looked at, and given a target
>>>>>>>> release tag, etc. Time for some bug triage. I don't think there has
>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>
>>>>>>>>
>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>> Have I missed something?
>>>>>>>>
>>>>>>>> =========================
>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>> Strategic Power Office with Supplier
>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>
>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>
>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>
>>>>>>>>
>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>
>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>
>>>>>>>>>> There are a number of bugs that have to be resolved before release
>>>>>>>>>> remember this is a volunteer effort so there is no full time person
>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>
>>>>>>>>> What are you basing this on?
>>>>>>>>>
>>>>>>>>>> once they are completed and testing has been done then there will
>>>>>>>>>> be a release.
>>>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>>>
>>>>>>>>> What are you basing this on? Maybe there is some confusion... the
>>>>>>>>> date on a release is the date it was branched from the trunk, not
>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>
>>>>>>>>> -David
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release date?
>>>>>>>>>>> Just curious.

[Scott Gray-2]

OFBIZ-3912 is a good example of an issue that is critical to an individual rather than the community I think.  A good indicator is that it has been broken for 5 months before being reported, can't be that critical then huh?

Regards
Scott

On 31/08/2010, at 9:45 PM, Jacques Le Roux wrote:

> Scott Gray wrote:
>> A blocking bug IMO is nothing more than the community (rather than an individual) deciding that a bug is important enough that a
>> release shouldn't occur until it is fixed.  I don't think we need any criteria other than that really.
>
> Yes that's fine to me. And a critical (for instance at https://issues.apache.org/jira/browse/OFBIZ-3912)?
>
> Jacques
>> Regards
>> Scott
>> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>>> Hey Scott, that's right!
>>> Happy to close this one. So eventually you were right, there are ANY blocking bugs in OFBiz under our criteria ;o)
>>> Though I guess we should better define our criteria for blocking. Because if we allow to use blocking only for bugs blocking all
>>> OFBiz there should be hardly any such bugs. I mean it would be very, very quickly fixed and we would have hardly the time to
>>> create a blocking bug. Notbaly because we have now BuildBot running and all commiters are quickly aware of any errors they
>>> woulds have made. Did you thought about it Scott, what is your perception?   Thanks
>>> Jacques
>>> Scott Gray wrote:
>>>> Hi Jacques,
>>>> I thought you fixed OFBIZ-3837 recently?  Or was that some other shipping estimate problem you were working on?
>>>> Regards
>>>> Scott
>>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 are reopened.
>>>>> This is againt all versions. There are only 78 for trunk but this is not a reliable criteria (if any are)
>>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. But I guess not under Scott's criteria (it's not
>>>>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 are critical and 173 major
>>>>> No needs to say that any help to clean things would be really appreciated...
>>>>> HTH
>>>>> Jacques
>>>>> From: "BJ Freeman" <[hidden email]>
>>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>> =========================
>>>>>> BJ Freeman  <http://bjfreeman.elance.com>
>>>>>> Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>> Specialtymarket.com  <http://www.specialtymarket.com/>
>>>>>> Systems Integrator-- Glad to Assist
>>>>>> Chat  Y! messenger: bjfr33man
>>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>>> Actually I meant a response to it like there are no bugs that fit this
>>>>>>> condition.
>>>>>>> =========================
>>>>>>> BJ Freeman <http://bjfreeman.elance.com>
>>>>>>> Strategic Power Office with Supplier Automation
>>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>> Specialtymarket.com <http://www.specialtymarket.com/>
>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>>> You missed something by reading an email from a community member and
>>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>> Regards
>>>>>>>> Scott
>>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>>> I was reffering to this:
>>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>>> I guess the basic questions might be: Did we have an official "freeze"
>>>>>>>>>> process where we only accepted bug fixes against that branch? Do we
>>>>>>>>>> have
>>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>> I agree. At least *all* bugs should be looked at, and given a target
>>>>>>>>> release tag, etc. Time for some bug triage. I don't think there has
>>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>>> Have I missed something?
>>>>>>>>> =========================
>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>>> There are a number of bugs that have to be resolved before release
>>>>>>>>>>> remember this is a volunteer effort so there is no full time person
>>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>> What are you basing this on?
>>>>>>>>>>> once they are completed and testing has been done then there will
>>>>>>>>>>> be a release.
>>>>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>>>> What are you basing this on? Maybe there is some confusion... the
>>>>>>>>>> date on a release is the date it was branched from the trunk, not
>>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>> -David
>>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release date?
>>>>>>>>>>>> Just curious.
>

[Malin Nicolas]

I agree with you Scott after it's really a vision problem. When I choose
a criteria level, I don't look to existant problems but the impact of a
bug for the community. If OFBiz contains several bugs for me, I use
production addon for my customer so as each bug is trivial  and after I
think to importance for the community.

Nicolas

Jacques Le Roux a écrit :

> Scott Gray wrote:
>> A blocking bug IMO is nothing more than the community (rather than an
>> individual) deciding that a bug is important enough that a
>> release shouldn't occur until it is fixed.  I don't think we need any
>> criteria other than that really.
>
> Yes that's fine to me. And a critical (for instance at
> https://issues.apache.org/jira/browse/OFBIZ-3912)?
>
> Jacques
>
>> Regards
>> Scott
>>
>> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>>
>>> Hey Scott, that's right!
>>>
>>> Happy to close this one. So eventually you were right, there are ANY
>>> blocking bugs in OFBiz under our criteria ;o)
>>>
>>> Though I guess we should better define our criteria for blocking.
>>> Because if we allow to use blocking only for bugs blocking all
>>> OFBiz there should be hardly any such bugs. I mean it would be very,
>>> very quickly fixed and we would have hardly the time to
>>> create a blocking bug. Notbaly because we have now BuildBot running
>>> and all commiters are quickly aware of any errors they
>>> woulds have made. Did you thought about it Scott, what is your
>>> perception?  
>>> Thanks
>>>
>>> Jacques
>>>
>>> Scott Gray wrote:
>>>> Hi Jacques,
>>>>
>>>> I thought you fixed OFBIZ-3837 recently?  Or was that some other
>>>> shipping estimate problem you were working on?
>>>>
>>>> Regards
>>>> Scott
>>>>
>>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>>
>>>>> There are currently 275 UNRESOLVED bugs, 11 have patches
>>>>> available, 14 are reopened.
>>>>> This is againt all versions. There are only 78 for trunk but this
>>>>> is not a reliable criteria (if any are)
>>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as
>>>>> blocking. But I guess not under Scott's criteria (it's not
>>>>> blocking OFBiz, just blocking a part of it, so it's critical
>>>>> actually) 4 are critical and 173 major
>>>>>
>>>>> No needs to say that any help to clean things would be really
>>>>> appreciated...
>>>>>
>>>>> HTH
>>>>>
>>>>> Jacques
>>>>>
>>>>> From: "BJ Freeman" <[hidden email]>
>>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>>
>>>>>> =========================
>>>>>> BJ Freeman  <http://bjfreeman.elance.com>
>>>>>> Strategic Power Office with Supplier Automation  
>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>> Specialtymarket.com  <http://www.specialtymarket.com/>
>>>>>> Systems Integrator-- Glad to Assist
>>>>>>
>>>>>> Chat  Y! messenger: bjfr33man
>>>>>>
>>>>>>
>>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>>> Actually I meant a response to it like there are no bugs that
>>>>>>> fit this
>>>>>>> condition.
>>>>>>>
>>>>>>> =========================
>>>>>>> BJ Freeman <http://bjfreeman.elance.com>
>>>>>>> Strategic Power Office with Supplier Automation
>>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>> Specialtymarket.com <http://www.specialtymarket.com/>
>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>
>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>
>>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>>
>>>>>>>
>>>>>>>> You missed something by reading an email from a community
>>>>>>>> member and
>>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Scott
>>>>>>>>
>>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>>
>>>>>>>>> I was reffering to this:
>>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>>> I guess the basic questions might be: Did we have an official
>>>>>>>>>> "freeze"
>>>>>>>>>> process where we only accepted bug fixes against that branch?
>>>>>>>>>> Do we
>>>>>>>>>> have
>>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>>
>>>>>>>>> I agree. At least *all* bugs should be looked at, and given a
>>>>>>>>> target
>>>>>>>>> release tag, etc. Time for some bug triage. I don't think
>>>>>>>>> there has
>>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>>> Have I missed something?
>>>>>>>>>
>>>>>>>>> =========================
>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>
>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>>
>>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>>
>>>>>>>>>>> There are a number of bugs that have to be resolved before
>>>>>>>>>>> release
>>>>>>>>>>> remember this is a volunteer effort so there is no full time
>>>>>>>>>>> person
>>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>>
>>>>>>>>>> What are you basing this on?
>>>>>>>>>>
>>>>>>>>>>> once they are completed and testing has been done then there
>>>>>>>>>>> will
>>>>>>>>>>> be a release.
>>>>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>>>>
>>>>>>>>>> What are you basing this on? Maybe there is some confusion...
>>>>>>>>>> the
>>>>>>>>>> date on a release is the date it was branched from the trunk,
>>>>>>>>>> not
>>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>>
>>>>>>>>>> -David
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected
>>>>>>>>>>>> release date?
>>>>>>>>>>>> Just curious.
>

[Erwan de FERRIERES]

Le 31/08/2010 11:56, Scott Gray a écrit :
> OFBIZ-3912 is a good example of an issue that is critical to an individual rather than the community I think.  A good indicator is that it has been broken for 5 months before being reported, can't be that critical then huh?
>
> Regards
> Scott

Hi,
lucene is broken since a long time in trunk... I think this is critical,
but the communauty don't... And this hasn't stopped us making a release..

Cheers,

--
Erwan de FERRIERES
www.nereide.biz

[Jacques Le Roux]

Hi Erwan,

Is there a Jira reporting this, with a patch?

Thanks

Jacques

Erwan de FERRIERES wrote:

> Le 31/08/2010 11:56, Scott Gray a écrit :
>> OFBIZ-3912 is a good example of an issue that is critical to an individual rather than the community I think.  A good indicator
>> is that it has been broken for 5 months before being reported, can't be that critical then huh? Regards
>> Scott
>
> Hi,
> lucene is broken since a long time in trunk... I think this is critical,
> but the communauty don't... And this hasn't stopped us making a release..
>
> Cheers,

[Erwan de FERRIERES]

Le 31/08/2010 12:31, Jacques Le Roux a écrit :
> Hi Erwan,
>
> Is there a Jira reporting this, with a patch?
>
> Thanks
>
> Jacques
>
Strangely, there is no jira... but here is the thread showing the
problem :
http://ofbiz.135035.n4.nabble.com/Lucene-is-broken-td2123400.html#a2123871
I may have only reported the problem to the mailing list... And so,
there is no patch. Be that is one was existing I would have commited it !
Cheers,

--
Erwan de FERRIERES
www.nereide.biz

[c.schinzer]

Incredible how the original topic now turned into something pretty different
... it's just great!

Matt, if you are still following this, I have a recommendation to make for
your original point 3.
You should start versioning your own releases (I do the same) and integrate
a later revision of OFBiz every now and then.

The trick is know as Subversion "Vendor Branch" and it is described in
detail here:
http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html

Try it out and you will see: after some 2-3 updates from the vendor's
repository (in this case OFBiz'), you will feel safe with the procedure. And
you should then also be able to automate it using scripting.

I still recommend you use an official release branch of OFBiz rather than
trunk, but using this recommendation will actually allow you to do
"fallbacks" on arbitrary versions of OFBiz trunk as long as you are
consequently tagging your own releases.
I do also recommend a testing stage before committing to your local
repository and rolling on to production.
Pros and cons on these latter two points have been addressed in the trail
already.

Hope this helps!

Regards


Carsten

[Jacques Le Roux]

From: "Carsten Schinzer" <[hidden email]>
> Incredible how the original topic now turned into something pretty different
> ... it's just great!

Yes :D  Actually Matt 1st hacked Jonatan's thread Error generating PDF invoice
http://markmail.org/message/vmon3ig3smles7k3

Jacques
 
> Matt, if you are still following this, I have a recommendation to make for
> your original point 3.
> You should start versioning your own releases (I do the same) and integrate
> a later revision of OFBiz every now and then.
>
> The trick is know as Subversion "Vendor Branch" and it is described in
> detail here:
> http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html

There are also alternatives suggested in wiki
https://cwiki.apache.org/confluence/display/OFBIZ/Online+Developers+Section

Jacques

> Try it out and you will see: after some 2-3 updates from the vendor's
> repository (in this case OFBiz'), you will feel safe with the procedure. And
> you should then also be able to automate it using scripting.
>
> I still recommend you use an official release branch of OFBiz rather than
> trunk, but using this recommendation will actually allow you to do
> "fallbacks" on arbitrary versions of OFBiz trunk as long as you are
> consequently tagging your own releases.
> I do also recommend a testing stage before committing to your local
> repository and rolling on to production.
> Pros and cons on these latter two points have been addressed in the trail
> already.
>
> Hope this helps!
>
> Regards
>
>
> Carsten
>

[BJ Freeman]

I am Glad for this discussion.
My years on Design teams had a lot different criteria.

so to Summarize if something is broke and no one wants to work on it, it
is not considered a bug.

As far as buildbot it is only as good as the tests written that it uses
and as was pointed out on the dev list ofbiz UI and minilanq is not
tested, as in the math error.

So the fact it "passed" a build only says the test so far, don't fail,
not that ofbiz is bug free.


reminds me of a used car salesman.


=========================
BJ Freeman  <http://bjfreeman.elance.com>
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Scott Gray sent the following on 8/31/2010 2:56 AM:

> OFBIZ-3912 is a good example of an issue that is critical to an individual rather than the community I think.  A good indicator is that it has been broken for 5 months before being reported, can't be that critical then huh?
>
> Regards
> Scott
>
> On 31/08/2010, at 9:45 PM, Jacques Le Roux wrote:
>
>> Scott Gray wrote:
>>> A blocking bug IMO is nothing more than the community (rather than an individual) deciding that a bug is important enough that a
>>> release shouldn't occur until it is fixed.  I don't think we need any criteria other than that really.
>>
>> Yes that's fine to me. And a critical (for instance at https://issues.apache.org/jira/browse/OFBIZ-3912)?
>>
>> Jacques
>>> Regards
>>> Scott
>>> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>>>> Hey Scott, that's right!
>>>> Happy to close this one. So eventually you were right, there are ANY blocking bugs in OFBiz under our criteria ;o)
>>>> Though I guess we should better define our criteria for blocking. Because if we allow to use blocking only for bugs blocking all
>>>> OFBiz there should be hardly any such bugs. I mean it would be very, very quickly fixed and we would have hardly the time to
>>>> create a blocking bug. Notbaly because we have now BuildBot running and all commiters are quickly aware of any errors they
>>>> woulds have made. Did you thought about it Scott, what is your perception?   Thanks
>>>> Jacques
>>>> Scott Gray wrote:
>>>>> Hi Jacques,
>>>>> I thought you fixed OFBIZ-3837 recently?  Or was that some other shipping estimate problem you were working on?
>>>>> Regards
>>>>> Scott
>>>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>>>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 are reopened.
>>>>>> This is againt all versions. There are only 78 for trunk but this is not a reliable criteria (if any are)
>>>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. But I guess not under Scott's criteria (it's not
>>>>>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 are critical and 173 major
>>>>>> No needs to say that any help to clean things would be really appreciated...
>>>>>> HTH
>>>>>> Jacques
>>>>>> From: "BJ Freeman"<[hidden email]>
>>>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>>> =========================
>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>> Strategic Power Office with Supplier Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>> Chat  Y! messenger: bjfr33man
>>>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>>>> Actually I meant a response to it like there are no bugs that fit this
>>>>>>>> condition.
>>>>>>>> =========================
>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>> Strategic Power Office with Supplier Automation
>>>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>>>> You missed something by reading an email from a community member and
>>>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>>> Regards
>>>>>>>>> Scott
>>>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>>>> I was reffering to this:
>>>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>>>> I guess the basic questions might be: Did we have an official "freeze"
>>>>>>>>>>> process where we only accepted bug fixes against that branch? Do we
>>>>>>>>>>> have
>>>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>>> I agree. At least *all* bugs should be looked at, and given a target
>>>>>>>>>> release tag, etc. Time for some bug triage. I don't think there has
>>>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>>>> Have I missed something?
>>>>>>>>>> =========================
>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>>>> There are a number of bugs that have to be resolved before release
>>>>>>>>>>>> remember this is a volunteer effort so there is no full time person
>>>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>>> What are you basing this on?
>>>>>>>>>>>> once they are completed and testing has been done then there will
>>>>>>>>>>>> be a release.
>>>>>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>>>>> What are you basing this on? Maybe there is some confusion... the
>>>>>>>>>>> date on a release is the date it was branched from the trunk, not
>>>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>>> -David
>>>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release date?
>>>>>>>>>>>>> Just curious.
>>
>

[Matt Warnock]

I am still following, and have been surprised at what I started...
It *IS* great!  :-)

Thanks for the tip, I'll try that right away.  Thanks again.
--
Matt Warnock <[hidden email]>
RidgeCrest Herbals, Inc.

On Tue, 2010-08-31 at 14:23 +0200, Carsten Schinzer wrote:

> Incredible how the original topic now turned into something pretty different
> ... it's just great!
>
> Matt, if you are still following this, I have a recommendation to make for
> your original point 3.
> You should start versioning your own releases (I do the same) and integrate
> a later revision of OFBiz every now and then.
>
> The trick is know as Subversion "Vendor Branch" and it is described in
> detail here:
> http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html
>
> Try it out and you will see: after some 2-3 updates from the vendor's
> repository (in this case OFBiz'), you will feel safe with the procedure. And
> you should then also be able to automate it using scripting.
>
> I still recommend you use an official release branch of OFBiz rather than
> trunk, but using this recommendation will actually allow you to do
> "fallbacks" on arbitrary versions of OFBiz trunk as long as you are
> consequently tagging your own releases.
> I do also recommend a testing stage before committing to your local
> repository and rolling on to production.
> Pros and cons on these latter two points have been addressed in the trail
> already.
>
> Hope this helps!
>
> Regards
>
>
> Carsten

[Jacques Le Roux]

From: "BJ Freeman" <[hidden email]>
>I am Glad for this discussion.
> My years on Design teams had a lot different criteria.
>
> so to Summarize if something is broke and no one wants to work on it, it is not considered a bug.

I don't think so, it's considered a bug but not a blocking nor a critical one.

> As far as buildbot it is only as good as the tests written that it uses and as was pointed out on the dev list ofbiz UI and
> minilanq is not tested, as in the math error.
>
> So the fact it "passed" a build only says the test so far, don't fail, not that ofbiz is bug free.

I was told one day (15 years ago, I guess), that, at this time, for Word (remember Window 95, tadaaa...), Microsoft had a team of 10
to 20 devs and at all between 120 to 150 persons Still the testers/dev ratio was less than 10 (much administrative people too make
the glue). At the NASA (not sure the period), for embedded software the ratio was 100! But don't take me wrong, I don't mean that we
need more bureaucracy ;o)

> reminds me of a used car salesman.

I never get there, else I buy a new one (I did once), or rather I buy it from owner to owner (I know mechanic).
Anyway, it's still far better than what he had a couple years ago (not my car)... Hopefully it will be far better in 2 years (still
not my car)...

Jacques

>
> =========================
> BJ Freeman  <http://bjfreeman.elance.com>
> Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com  <http://www.specialtymarket.com/>
> Systems Integrator-- Glad to Assist
>
> Chat  Y! messenger: bjfr33man
> Scott Gray sent the following on 8/31/2010 2:56 AM:
>
>> OFBIZ-3912 is a good example of an issue that is critical to an individual rather than the community I think.  A good indicator
>> is that it has been broken for 5 months before being reported, can't be that critical then huh?
>>
>> Regards
>> Scott
>>
>> On 31/08/2010, at 9:45 PM, Jacques Le Roux wrote:
>>
>>> Scott Gray wrote:
>>>> A blocking bug IMO is nothing more than the community (rather than an individual) deciding that a bug is important enough that
>>>> a
>>>> release shouldn't occur until it is fixed.  I don't think we need any criteria other than that really.
>>>
>>> Yes that's fine to me. And a critical (for instance at https://issues.apache.org/jira/browse/OFBIZ-3912)?
>>>
>>> Jacques
>>>> Regards
>>>> Scott
>>>> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>>>>> Hey Scott, that's right!
>>>>> Happy to close this one. So eventually you were right, there are ANY blocking bugs in OFBiz under our criteria ;o)
>>>>> Though I guess we should better define our criteria for blocking. Because if we allow to use blocking only for bugs blocking
>>>>> all
>>>>> OFBiz there should be hardly any such bugs. I mean it would be very, very quickly fixed and we would have hardly the time to
>>>>> create a blocking bug. Notbaly because we have now BuildBot running and all commiters are quickly aware of any errors they
>>>>> woulds have made. Did you thought about it Scott, what is your perception?   Thanks
>>>>> Jacques
>>>>> Scott Gray wrote:
>>>>>> Hi Jacques,
>>>>>> I thought you fixed OFBIZ-3837 recently?  Or was that some other shipping estimate problem you were working on?
>>>>>> Regards
>>>>>> Scott
>>>>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>>>>> There are currently 275 UNRESOLVED bugs, 11 have patches available, 14 are reopened.
>>>>>>> This is againt all versions. There are only 78 for trunk but this is not a reliable criteria (if any are)
>>>>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as blocking. But I guess not under Scott's criteria (it's not
>>>>>>> blocking OFBiz, just blocking a part of it, so it's critical actually) 4 are critical and 173 major
>>>>>>> No needs to say that any help to clean things would be really appreciated...
>>>>>>> HTH
>>>>>>> Jacques
>>>>>>> From: "BJ Freeman"<[hidden email]>
>>>>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>>>> =========================
>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>> Strategic Power Office with Supplier Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>> Chat  Y! messenger: bjfr33man
>>>>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>>>>> Actually I meant a response to it like there are no bugs that fit this
>>>>>>>>> condition.
>>>>>>>>> =========================
>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>> Strategic Power Office with Supplier Automation
>>>>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>>>>> You missed something by reading an email from a community member and
>>>>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>>>> Regards
>>>>>>>>>> Scott
>>>>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>>>>> I was reffering to this:
>>>>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>>>>> I guess the basic questions might be: Did we have an official "freeze"
>>>>>>>>>>>> process where we only accepted bug fixes against that branch? Do we
>>>>>>>>>>>> have
>>>>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>>>> I agree. At least *all* bugs should be looked at, and given a target
>>>>>>>>>>> release tag, etc. Time for some bug triage. I don't think there has
>>>>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>>>>> Have I missed something?
>>>>>>>>>>> =========================
>>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>>>>> There are a number of bugs that have to be resolved before release
>>>>>>>>>>>>> remember this is a volunteer effort so there is no full time person
>>>>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>>>> What are you basing this on?
>>>>>>>>>>>>> once they are completed and testing has been done then there will
>>>>>>>>>>>>> be a release.
>>>>>>>>>>>>> right now we are about 4 months past the planned release date.
>>>>>>>>>>>> What are you basing this on? Maybe there is some confusion... the
>>>>>>>>>>>> date on a release is the date it was branched from the trunk, not
>>>>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>>>> -David
>>>>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected release date?
>>>>>>>>>>>>>> Just curious.
>>>
>>
>

[Jacques Le Roux]

Hi Matt,

Not a big deal, but yes it's not a good practice and I was corrected many times at my own beginning, that why I remember it well :o)
Actually when it's a different subject, for the sake of clairity you should open a new thread by creating an entirely new message
and not responding to an existing one. Because these last one contains information in its header which will hook it on the thread it
belongs

Thanks to care

Jacques

From: "Matt Warnock" <[hidden email]>

> Hmm.  I usually just reply to an existing thread, but change the subject
> line to create a new thread.  It sounds from your comment like that may
> not be good practice.  Is there some thread identification code in the
> header, usually invisible in mail clients, that I was not aware of?
>
> If so, my apologies to everyone.  I usually read this in Evolution on
> Ubuntu, and was not aware of the issue, as it doesn't show there.
> --
> Matt Warnock <[hidden email]>
> RidgeCrest Herbals, Inc.
>
> On Tue, 2010-08-31 at 14:45 +0200, Jacques Le Roux wrote:
>> From: "Carsten Schinzer" <[hidden email]>
>> > Incredible how the original topic now turned into something pretty different
>> > ... it's just great!
>>
>> Yes :D  Actually Matt 1st hacked Jonatan's thread Error generating PDF invoice
>> http://markmail.org/message/vmon3ig3smles7k3
>>
>> Jacques
>>
>> > Matt, if you are still following this, I have a recommendation to make for
>> > your original point 3.
>> > You should start versioning your own releases (I do the same) and integrate
>> > a later revision of OFBiz every now and then.
>> >
>> > The trick is know as Subversion "Vendor Branch" and it is described in
>> > detail here:
>> > http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html
>>
>> There are also alternatives suggested in wiki
>> https://cwiki.apache.org/confluence/display/OFBIZ/Online+Developers+Section
>>
>> Jacques
>>
>> > Try it out and you will see: after some 2-3 updates from the vendor's
>> > repository (in this case OFBiz'), you will feel safe with the procedure. And
>> > you should then also be able to automate it using scripting.
>> >
>> > I still recommend you use an official release branch of OFBiz rather than
>> > trunk, but using this recommendation will actually allow you to do
>> > "fallbacks" on arbitrary versions of OFBiz trunk as long as you are
>> > consequently tagging your own releases.
>> > I do also recommend a testing stage before committing to your local
>> > repository and rolling on to production.
>> > Pros and cons on these latter two points have been addressed in the trail
>> > already.
>> >
>> > Hope this helps!
>> >
>> > Regards
>> >
>> >
>> > Carsten
>> >
>

[BJ Freeman]

ah yes I do remember win9x, I was on the Microsoft Campus during the
time working on a different project.
there was a room of about 200 machines of different configurations
(speed, memory, os settings) that ran the application under test.
There were no tester but Test engineers(5-20) that built test scenarios
in Microsoft own Test software. Their software tested from the UI down
to the core subroutines.
if something was broke is was given a priority as blocking to trivial
like jira.
this just set what was worked on first. however all were resolved.

let me say I am not saying that ofbiz should be at this level, only that
it should be accurate about what is the reality of ofbiz state.

and yes since 2002 ofbiz has come a long way and most of the newbies
don't know what they missed (cough cough).




=========================
BJ Freeman  <http://bjfreeman.elance.com>
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man


Jacques Le Roux sent the following on 8/31/2010 10:22 AM:

> From: "BJ Freeman" <[hidden email]>
>> I am Glad for this discussion.
>> My years on Design teams had a lot different criteria.
>>
>> so to Summarize if something is broke and no one wants to work on it,
>> it is not considered a bug.
>
> I don't think so, it's considered a bug but not a blocking nor a
> critical one.
>
>> As far as buildbot it is only as good as the tests written that it
>> uses and as was pointed out on the dev list ofbiz UI and minilanq is
>> not tested, as in the math error.
>>
>> So the fact it "passed" a build only says the test so far, don't fail,
>> not that ofbiz is bug free.
>
> I was told one day (15 years ago, I guess), that, at this time, for Word
> (remember Window 95, tadaaa...), Microsoft had a team of 10 to 20 devs
> and at all between 120 to 150 persons Still the testers/dev ratio was
> less than 10 (much administrative people too make the glue). At the NASA
> (not sure the period), for embedded software the ratio was 100! But
> don't take me wrong, I don't mean that we need more bureaucracy ;o)
>
>> reminds me of a used car salesman.
>
> I never get there, else I buy a new one (I did once), or rather I buy it
> from owner to owner (I know mechanic).
> Anyway, it's still far better than what he had a couple years ago (not
> my car)... Hopefully it will be far better in 2 years (still not my car)...
>
> Jacques
>
>>
>> =========================
>> BJ Freeman <http://bjfreeman.elance.com>
>> Strategic Power Office with Supplier Automation
>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>> Specialtymarket.com <http://www.specialtymarket.com/>
>> Systems Integrator-- Glad to Assist
>>
>> Chat Y! messenger: bjfr33man
>> Scott Gray sent the following on 8/31/2010 2:56 AM:
>>
>>> OFBIZ-3912 is a good example of an issue that is critical to an
>>> individual rather than the community I think. A good indicator is
>>> that it has been broken for 5 months before being reported, can't be
>>> that critical then huh?
>>>
>>> Regards
>>> Scott
>>>
>>> On 31/08/2010, at 9:45 PM, Jacques Le Roux wrote:
>>>
>>>> Scott Gray wrote:
>>>>> A blocking bug IMO is nothing more than the community (rather than
>>>>> an individual) deciding that a bug is important enough that a
>>>>> release shouldn't occur until it is fixed. I don't think we need
>>>>> any criteria other than that really.
>>>>
>>>> Yes that's fine to me. And a critical (for instance at
>>>> https://issues.apache.org/jira/browse/OFBIZ-3912)?
>>>>
>>>> Jacques
>>>>> Regards
>>>>> Scott
>>>>> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>>>>>> Hey Scott, that's right!
>>>>>> Happy to close this one. So eventually you were right, there are
>>>>>> ANY blocking bugs in OFBiz under our criteria ;o)
>>>>>> Though I guess we should better define our criteria for blocking.
>>>>>> Because if we allow to use blocking only for bugs blocking all
>>>>>> OFBiz there should be hardly any such bugs. I mean it would be
>>>>>> very, very quickly fixed and we would have hardly the time to
>>>>>> create a blocking bug. Notbaly because we have now BuildBot
>>>>>> running and all commiters are quickly aware of any errors they
>>>>>> woulds have made. Did you thought about it Scott, what is your
>>>>>> perception? Thanks
>>>>>> Jacques
>>>>>> Scott Gray wrote:
>>>>>>> Hi Jacques,
>>>>>>> I thought you fixed OFBIZ-3837 recently? Or was that some other
>>>>>>> shipping estimate problem you were working on?
>>>>>>> Regards
>>>>>>> Scott
>>>>>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>>>>>> There are currently 275 UNRESOLVED bugs, 11 have patches
>>>>>>>> available, 14 are reopened.
>>>>>>>> This is againt all versions. There are only 78 for trunk but
>>>>>>>> this is not a reliable criteria (if any are)
>>>>>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as
>>>>>>>> blocking. But I guess not under Scott's criteria (it's not
>>>>>>>> blocking OFBiz, just blocking a part of it, so it's critical
>>>>>>>> actually) 4 are critical and 173 major
>>>>>>>> No needs to say that any help to clean things would be really
>>>>>>>> appreciated...
>>>>>>>> HTH
>>>>>>>> Jacques
>>>>>>>> From: "BJ Freeman"<[hidden email]>
>>>>>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>>>>> =========================
>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>
>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>>>>>> Actually I meant a response to it like there are no bugs that
>>>>>>>>>> fit this
>>>>>>>>>> condition.
>>>>>>>>>> =========================
>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>> Strategic Power Office with Supplier Automation
>>>>>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>>>>>> You missed something by reading an email from a community
>>>>>>>>>>> member and
>>>>>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>>>>> Regards
>>>>>>>>>>> Scott
>>>>>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>>>>>> I was reffering to this:
>>>>>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>>>>>> I guess the basic questions might be: Did we have an
>>>>>>>>>>>>> official "freeze"
>>>>>>>>>>>>> process where we only accepted bug fixes against that
>>>>>>>>>>>>> branch? Do we
>>>>>>>>>>>>> have
>>>>>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>>>>> I agree. At least *all* bugs should be looked at, and given
>>>>>>>>>>>> a target
>>>>>>>>>>>> release tag, etc. Time for some bug triage. I don't think
>>>>>>>>>>>> there has
>>>>>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>>>>>> Have I missed something?
>>>>>>>>>>>> =========================
>>>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>>>>
>>>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>>>>>> There are a number of bugs that have to be resolved before
>>>>>>>>>>>>>> release
>>>>>>>>>>>>>> remember this is a volunteer effort so there is no full
>>>>>>>>>>>>>> time person
>>>>>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>>>>> What are you basing this on?
>>>>>>>>>>>>>> once they are completed and testing has been done then
>>>>>>>>>>>>>> there will
>>>>>>>>>>>>>> be a release.
>>>>>>>>>>>>>> right now we are about 4 months past the planned release
>>>>>>>>>>>>>> date.
>>>>>>>>>>>>> What are you basing this on? Maybe there is some
>>>>>>>>>>>>> confusion... the
>>>>>>>>>>>>> date on a release is the date it was branched from the
>>>>>>>>>>>>> trunk, not
>>>>>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>>>>> -David
>>>>>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected
>>>>>>>>>>>>>>> release date?
>>>>>>>>>>>>>>> Just curious.
>>>>
>>>
>>
>
>
>

[Jacques Le Roux]

Fortunately we have now Selenium and Junit. We should be able to do better, but you are right, it's not a simple task and moreover
not very appealing for most of ordinary mortals

Jacques

From: "BJ Freeman" <[hidden email]>

> ah yes I do remember win9x, I was on the Microsoft Campus during the
> time working on a different project.
> there was a room of about 200 machines of different configurations
> (speed, memory, os settings) that ran the application under test.
> There were no tester but Test engineers(5-20) that built test scenarios
> in Microsoft own Test software. Their software tested from the UI down
> to the core subroutines.
> if something was broke is was given a priority as blocking to trivial
> like jira.
> this just set what was worked on first. however all were resolved.
>
> let me say I am not saying that ofbiz should be at this level, only that
> it should be accurate about what is the reality of ofbiz state.
>
> and yes since 2002 ofbiz has come a long way and most of the newbies
> don't know what they missed (cough cough).
>
>
>
>
> =========================
> BJ Freeman  <http://bjfreeman.elance.com>
> Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com  <http://www.specialtymarket.com/>
> Systems Integrator-- Glad to Assist
>
> Chat  Y! messenger: bjfr33man
>
>
> Jacques Le Roux sent the following on 8/31/2010 10:22 AM:
>> From: "BJ Freeman" <[hidden email]>
>>> I am Glad for this discussion.
>>> My years on Design teams had a lot different criteria.
>>>
>>> so to Summarize if something is broke and no one wants to work on it,
>>> it is not considered a bug.
>>
>> I don't think so, it's considered a bug but not a blocking nor a
>> critical one.
>>
>>> As far as buildbot it is only as good as the tests written that it
>>> uses and as was pointed out on the dev list ofbiz UI and minilanq is
>>> not tested, as in the math error.
>>>
>>> So the fact it "passed" a build only says the test so far, don't fail,
>>> not that ofbiz is bug free.
>>
>> I was told one day (15 years ago, I guess), that, at this time, for Word
>> (remember Window 95, tadaaa...), Microsoft had a team of 10 to 20 devs
>> and at all between 120 to 150 persons Still the testers/dev ratio was
>> less than 10 (much administrative people too make the glue). At the NASA
>> (not sure the period), for embedded software the ratio was 100! But
>> don't take me wrong, I don't mean that we need more bureaucracy ;o)
>>
>>> reminds me of a used car salesman.
>>
>> I never get there, else I buy a new one (I did once), or rather I buy it
>> from owner to owner (I know mechanic).
>> Anyway, it's still far better than what he had a couple years ago (not
>> my car)... Hopefully it will be far better in 2 years (still not my car)...
>>
>> Jacques
>>
>>>
>>> =========================
>>> BJ Freeman <http://bjfreeman.elance.com>
>>> Strategic Power Office with Supplier Automation
>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>> Specialtymarket.com <http://www.specialtymarket.com/>
>>> Systems Integrator-- Glad to Assist
>>>
>>> Chat Y! messenger: bjfr33man
>>> Scott Gray sent the following on 8/31/2010 2:56 AM:
>>>
>>>> OFBIZ-3912 is a good example of an issue that is critical to an
>>>> individual rather than the community I think. A good indicator is
>>>> that it has been broken for 5 months before being reported, can't be
>>>> that critical then huh?
>>>>
>>>> Regards
>>>> Scott
>>>>
>>>> On 31/08/2010, at 9:45 PM, Jacques Le Roux wrote:
>>>>
>>>>> Scott Gray wrote:
>>>>>> A blocking bug IMO is nothing more than the community (rather than
>>>>>> an individual) deciding that a bug is important enough that a
>>>>>> release shouldn't occur until it is fixed. I don't think we need
>>>>>> any criteria other than that really.
>>>>>
>>>>> Yes that's fine to me. And a critical (for instance at
>>>>> https://issues.apache.org/jira/browse/OFBIZ-3912)?
>>>>>
>>>>> Jacques
>>>>>> Regards
>>>>>> Scott
>>>>>> On 31/08/2010, at 9:09 PM, Jacques Le Roux wrote:
>>>>>>> Hey Scott, that's right!
>>>>>>> Happy to close this one. So eventually you were right, there are
>>>>>>> ANY blocking bugs in OFBiz under our criteria ;o)
>>>>>>> Though I guess we should better define our criteria for blocking.
>>>>>>> Because if we allow to use blocking only for bugs blocking all
>>>>>>> OFBiz there should be hardly any such bugs. I mean it would be
>>>>>>> very, very quickly fixed and we would have hardly the time to
>>>>>>> create a blocking bug. Notbaly because we have now BuildBot
>>>>>>> running and all commiters are quickly aware of any errors they
>>>>>>> woulds have made. Did you thought about it Scott, what is your
>>>>>>> perception? Thanks
>>>>>>> Jacques
>>>>>>> Scott Gray wrote:
>>>>>>>> Hi Jacques,
>>>>>>>> I thought you fixed OFBIZ-3837 recently? Or was that some other
>>>>>>>> shipping estimate problem you were working on?
>>>>>>>> Regards
>>>>>>>> Scott
>>>>>>>> On 31/08/2010, at 7:52 PM, Jacques Le Roux wrote:
>>>>>>>>> There are currently 275 UNRESOLVED bugs, 11 have patches
>>>>>>>>> available, 14 are reopened.
>>>>>>>>> This is againt all versions. There are only 78 for trunk but
>>>>>>>>> this is not a reliable criteria (if any are)
>>>>>>>>> https://issues.apache.org/jira/browse/OFBIZ-3837 is marked as
>>>>>>>>> blocking. But I guess not under Scott's criteria (it's not
>>>>>>>>> blocking OFBiz, just blocking a part of it, so it's critical
>>>>>>>>> actually) 4 are critical and 173 major
>>>>>>>>> No needs to say that any help to clean things would be really
>>>>>>>>> appreciated...
>>>>>>>>> HTH
>>>>>>>>> Jacques
>>>>>>>>> From: "BJ Freeman"<[hidden email]>
>>>>>>>>>> Quick scan of Jira shows 4 open bugs not counting mine.
>>>>>>>>>> =========================
>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>>
>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>> BJ Freeman sent the following on 8/30/2010 10:17 PM:
>>>>>>>>>>> Actually I meant a response to it like there are no bugs that
>>>>>>>>>>> fit this
>>>>>>>>>>> condition.
>>>>>>>>>>> =========================
>>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>>> Strategic Power Office with Supplier Automation
>>>>>>>>>>> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>>> Scott Gray sent the following on 8/30/2010 10:12 PM:
>>>>>>>>>>>> You missed something by reading an email from a community
>>>>>>>>>>>> member and
>>>>>>>>>>>> interpreting it's contents as some sort of official policy.
>>>>>>>>>>>> Regards
>>>>>>>>>>>> Scott
>>>>>>>>>>>> On 31/08/2010, at 5:07 PM, BJ Freeman wrote:
>>>>>>>>>>>>> I was reffering to this:
>>>>>>>>>>>>> On 07/29/2010 01:53 AM, Ean Schuessler wrote:
>>>>>>>>>>>>>> I guess the basic questions might be: Did we have an
>>>>>>>>>>>>>> official "freeze"
>>>>>>>>>>>>>> process where we only accepted bug fixes against that
>>>>>>>>>>>>>> branch? Do we
>>>>>>>>>>>>>> have
>>>>>>>>>>>>>> any open bugs that are considered "release critical"?
>>>>>>>>>>>>> I agree. At least *all* bugs should be looked at, and given
>>>>>>>>>>>>> a target
>>>>>>>>>>>>> release tag, etc. Time for some bug triage. I don't think
>>>>>>>>>>>>> there has
>>>>>>>>>>>>> been a concerted effort like that in like, forever.
>>>>>>>>>>>>> I have not seen anything that shows this as taken care of.
>>>>>>>>>>>>> Have I missed something?
>>>>>>>>>>>>> =========================
>>>>>>>>>>>>> BJ Freeman<http://bjfreeman.elance.com>
>>>>>>>>>>>>> Strategic Power Office with Supplier
>>>>>>>>>>>>> Automation<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Specialtymarket.com<http://www.specialtymarket.com/>
>>>>>>>>>>>>> Systems Integrator-- Glad to Assist
>>>>>>>>>>>>> Chat Y! messenger: bjfr33man
>>>>>>>>>>>>> David E Jones sent the following on 8/30/2010 9:47 PM:
>>>>>>>>>>>>>> On Aug 30, 2010, at 10:38 PM, BJ Freeman wrote:
>>>>>>>>>>>>>>> There are a number of bugs that have to be resolved before
>>>>>>>>>>>>>>> release
>>>>>>>>>>>>>>> remember this is a volunteer effort so there is no full
>>>>>>>>>>>>>>> time person
>>>>>>>>>>>>>>> doing the patches for the bugs.
>>>>>>>>>>>>>> What are you basing this on?
>>>>>>>>>>>>>>> once they are completed and testing has been done then
>>>>>>>>>>>>>>> there will
>>>>>>>>>>>>>>> be a release.
>>>>>>>>>>>>>>> right now we are about 4 months past the planned release
>>>>>>>>>>>>>>> date.
>>>>>>>>>>>>>> What are you basing this on? Maybe there is some
>>>>>>>>>>>>>> confusion... the
>>>>>>>>>>>>>> date on a release is the date it was branched from the
>>>>>>>>>>>>>> trunk, not
>>>>>>>>>>>>>> the date that a binary release is done from the branch.
>>>>>>>>>>>>>> -David
>>>>>>>>>>>>>>> Matt Warnock sent the following on 8/30/2010 9:27 PM:
>>>>>>>>>>>>>>>> Thanks. Is 10.04 nearing release? Is there an expected
>>>>>>>>>>>>>>>> release date?
>>>>>>>>>>>>>>>> Just curious.
>>>>>
>>>>
>>>
>>
>>
>>
>

[Jacques Le Roux]

Would you mind creating a Jira if you are able to easily reproduce on demo server?

TIA

Jacques

From: "Jonatan Soto" <[hidden email]>

> Answering to myself:
>
>
> On Mon, Aug 30, 2010 at 8:42 PM, Jonatan Soto <[hidden email]>wrote:
>
>> Has anyone got this error when an invoice PDF is generated?
>>
>> Expression x is undefined on line 19, column 15 in
>> component://accounting/webapp/accounting/invoice/invoiceReportItems.fo.ftl.
>>
>
> <#-- <#escape x as x?xml> --> I've commented this and the first error
> disappears. Seems that x variable is not defined neither used anywhere
> (AccountingPrintScreens.xml#InvoicePDF)
>
>
>> The problematic instruction:
>> ----------
>> ==> ${taxRate.description} escaped ${taxRate.description?xml} [on line 241,
>> column 23 in
>> component://accounting/webapp/accounting/invoice/invoiceReportItems.fo.ftl]
>> ----------
>>
>
> I just added a description to the tax rate and it works. I think it should
> be checked to avoid print it when the values are null or blank on the PDF
> generation because the description of a tax rate is not mandatory.
>
>>
>> Java backtrace for programmers:
>> ----------
>> freemarker.core.InvalidReferenceException: Expression x is undefined on
>> line 19, column 15 in
>> component://accounting/webapp/accounting/invoice/invoiceReportItems.fo.ftl.
>>
>> I'm running a two months old trunk version of Ofbiz.
>>
>> I'll try to fix and then I'll create a Jira with a patch if no one has
>> solved yet.
>>
>> Thanks in advance.
>>
>> --
>> -----
>>
>> Jonatan Soto
>>
>
>
>
> --
> -----
>
> Jonatan Soto
>