OFBiz › OFBiz - User

Error generating PDF invoice

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

37 messages Options

jonatan soto

Error generating PDF invoice

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.
The problematic instruction:
----------
==> ${taxRate.description} escaped ${taxRate.description?xml} [on line 241,
column 23 in
component://accounting/webapp/accounting/invoice/invoiceReportItems.fo.ftl]
----------

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

Re: Error generating PDF invoice

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

Matt Warnock

Best practices for updates from trunk

I run a small enterprise and I doubt our needs are unusual. We would
like to run trunk and stay (more or less) current. We're running
postgresql as a backend. I'm hoping to automate (as much as possible)
the update process. I'm hoping to implement a few things not provided
in the standard demo setup.

1) I need to backup the database nightly, so that our daily work doesn't
get lost (doh!). I can use pg_dump for that, but of course it backs up
the entire database, including seed, admin-user-login, and site-specific
data. I could also use the webtools dump, which I assume does the exact
same thing but in XML, which is a good deal larger in file size.
However, webtools won't write an XML file for an empty table, while
pg_dump would write a structure definition for that table. Probably
pg_dump would be a good deal faster. Size and speed issues aside, it
seems that neither method differentiates in any way between seed and
non-seed data. Am I correct here?

2) To effectively use the webtools backup, I would need to automate it
from a cron job. Is there an easy way to call ofbiz services from the
command line, or do I need to schedule a job within OFBiz to do this
kind of thing? What are the pros and cons of a system cron job vs. a
scheduled job in OFBiz?

3) I need a log of what version I was running when. For example, if I
update weekly, and on Sunday night I roll forward to the latest trunk
revision 970999, and it breaks something, I need to have a log that
tells me that Friday (when it worked) I was running 970888, so I can
roll back to that revision, until I get the kinks worked out with the
upgrade. Otherwise I have to restore from a dated backup, which I can
always do, but it seems that a simple "svn checkout 970888; ./ant build"
might be cleaner. I'm assuming that after updating the code with "svn
checkout" I can log the date/time to a file with the output of "svn
info".

4) If a revision requires a database update or modification, I would
like to know about it in advance, and make sure that manual modification
is completed before the upgrade. I'm assuming what I need there should
always be found in:
https://cwiki.apache.org/confluence/display/OFBTECH/Revisions+Requiring
+Data+Migration

5) I would like to update all seed data in place (postgresql) without
overwriting the rest of the (non-seed) data. Will executing "./ant
run-install-seed" overwrite the EXISTING seed data in a production
database without affecting the non-seed data? Or it it only intended
for use on an empty database, as all the examples I have found do? If
the latter, how do you restore only the NON-seed data after a seed data
initialization?

Are there any other bear traps or best practices that I should be aware
of? Or is this stuff documented somewhere that I have not found? There
was a discussion of it (at least the seed vs. demo data issue) about a
year ago on this list, but I didn't see these specific questions
answered.

Or am I overly optimistic about the possibility of updating a production
system regularly as OFBiz trunk changes?

Thanks in advance.

BJ Freeman

Re: Best practices for updates from trunk

Mat you speak of a combination of Migration conponent and Setup
Component now under design.
I covered most of this under the email subject
Migration component Ideas 8/26/2010
also as a expansion
see the dev list subjects
Step to automate Setup for entityengine.xml 8/26/20010
and
using derby for setup controller

also
https://issues.apache.org/jira/browse/OFBIZ-635

=========================
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
Matt Warnock sent the following on 8/30/2010 2:12 PM:

> I run a small enterprise and I doubt our needs are unusual. We would
> like to run trunk and stay (more or less) current. We're running
> postgresql as a backend. I'm hoping to automate (as much as possible)
> the update process. I'm hoping to implement a few things not provided
> in the standard demo setup.
>
> 1) I need to backup the database nightly, so that our daily work doesn't
> get lost (doh!). I can use pg_dump for that, but of course it backs up
> the entire database, including seed, admin-user-login, and site-specific
> data. I could also use the webtools dump, which I assume does the exact
> same thing but in XML, which is a good deal larger in file size.
> However, webtools won't write an XML file for an empty table, while
> pg_dump would write a structure definition for that table. Probably
> pg_dump would be a good deal faster. Size and speed issues aside, it
> seems that neither method differentiates in any way between seed and
> non-seed data. Am I correct here?
>
> 2) To effectively use the webtools backup, I would need to automate it
> from a cron job. Is there an easy way to call ofbiz services from the
> command line, or do I need to schedule a job within OFBiz to do this
> kind of thing? What are the pros and cons of a system cron job vs. a
> scheduled job in OFBiz?
>
> 3) I need a log of what version I was running when. For example, if I
> update weekly, and on Sunday night I roll forward to the latest trunk
> revision 970999, and it breaks something, I need to have a log that
> tells me that Friday (when it worked) I was running 970888, so I can
> roll back to that revision, until I get the kinks worked out with the
> upgrade. Otherwise I have to restore from a dated backup, which I can
> always do, but it seems that a simple "svn checkout 970888; ./ant build"
> might be cleaner. I'm assuming that after updating the code with "svn
> checkout" I can log the date/time to a file with the output of "svn
> info".
>
> 4) If a revision requires a database update or modification, I would
> like to know about it in advance, and make sure that manual modification
> is completed before the upgrade. I'm assuming what I need there should
> always be found in:
> https://cwiki.apache.org/confluence/display/OFBTECH/Revisions+Requiring
> +Data+Migration
>
> 5) I would like to update all seed data in place (postgresql) without
> overwriting the rest of the (non-seed) data. Will executing "./ant
> run-install-seed" overwrite the EXISTING seed data in a production
> database without affecting the non-seed data? Or it it only intended
> for use on an empty database, as all the examples I have found do? If
> the latter, how do you restore only the NON-seed data after a seed data
> initialization?
>
> Are there any other bear traps or best practices that I should be aware
> of? Or is this stuff documented somewhere that I have not found? There
> was a discussion of it (at least the seed vs. demo data issue) about a
> year ago on this list, but I didn't see these specific questions
> answered.
>
> Or am I overly optimistic about the possibility of updating a production
> system regularly as OFBiz trunk changes?
>
> Thanks in advance.
>
>

David E. Jones-2

Re: Best practices for updates from trunk

In reply to this post by Matt Warnock

Matt,

I wouldn't recommend updating a production instance against the trunk without testing. I generally do recommend to clients who are doing customizations or building on top of OFBiz that they update against the trunk frequently during development, and then stop before integration (general system) testing, or at least stop for their release candidate branch and continue updating against the OFBiz trunk for their development branch.

As for database changes, the Revisions+Requiring+Data+Migration page is manually updated and therefore not totally reliable. I'd recommend running the Check/Update database stuff in the Entity Engine by changing your entityengine.xml file to not automatically update anything (ie don't add new tables or columns, etc), and then look at the startup log or use webtools to see the differences between the current entity definitions and the meta-data in your database.

-David

On Aug 30, 2010, at 3:12 PM, Matt Warnock wrote:

Matt Warnock

Re: Best practices for updates from trunk

In reply to this post by BJ Freeman

Thanks, BJ, but I am looking for best practices on how to do it NOW, not
the automated component under design for the future. The emails you
mentioned don't really address any of the questions below. But neither
does any of the existing docs I have found so far. :-)

Pointers, anyone?

I did try "./ant run-install-seed" on an existing database (previously
created with "run-install"), it ran without obvious errors and the
number of rows changed that it reported was several thousand, but less
than the number with "run-install".

So can it (usually) be safely run on a production database, and will it
have the intended effect of updating the seed data (if necessary)
without deleting/overwriting the production data that may refer to that
seed data? From previous database experience, I know that
updating/removing/replacing data to which other data points is often a
problem, to say the least.

Also, are there any pros and cons for putting the OLAP datasource in a
separate database from the main data source? The existing derby demo
uses two, but most of the setup tutorials I find are pretty vague on
this point, but if I point both data sources to the same postgresql
database, I see no obvious errors. Am i asking for trouble down the
road? What is the difference between the two, and are there data
collisions I'm not seeing yet?

--
Matt Warnock <[hidden email]>
RidgeCrest Herbals, Inc.

On Mon, 2010-08-30 at 16:22 -0700, BJ Freeman wrote:

> Mat you speak of a combination of Migration conponent and Setup
> Component now under design.
> I covered most of this under the email subject
> Migration component Ideas 8/26/2010
> also as a expansion
> see the dev list subjects
> Step to automate Setup for entityengine.xml 8/26/20010
> and
> using derby for setup controller
>
> also
> https://issues.apache.org/jira/browse/OFBIZ-635
>
> =========================
> 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
> Matt Warnock sent the following on 8/30/2010 2:12 PM:
>
>
> > I run a small enterprise and I doubt our needs are unusual. We would
> > like to run trunk and stay (more or less) current. We're running
> > postgresql as a backend. I'm hoping to automate (as much as possible)
> > the update process. I'm hoping to implement a few things not provided
> > in the standard demo setup.
> >
> > 1) I need to backup the database nightly, so that our daily work doesn't
> > get lost (doh!). I can use pg_dump for that, but of course it backs up
> > the entire database, including seed, admin-user-login, and site-specific
> > data. I could also use the webtools dump, which I assume does the exact
> > same thing but in XML, which is a good deal larger in file size.
> > However, webtools won't write an XML file for an empty table, while
> > pg_dump would write a structure definition for that table. Probably
> > pg_dump would be a good deal faster. Size and speed issues aside, it
> > seems that neither method differentiates in any way between seed and
> > non-seed data. Am I correct here?
> >
> > 2) To effectively use the webtools backup, I would need to automate it
> > from a cron job. Is there an easy way to call ofbiz services from the
> > command line, or do I need to schedule a job within OFBiz to do this
> > kind of thing? What are the pros and cons of a system cron job vs. a
> > scheduled job in OFBiz?
> >
> > 3) I need a log of what version I was running when. For example, if I
> > update weekly, and on Sunday night I roll forward to the latest trunk
> > revision 970999, and it breaks something, I need to have a log that
> > tells me that Friday (when it worked) I was running 970888, so I can
> > roll back to that revision, until I get the kinks worked out with the
> > upgrade. Otherwise I have to restore from a dated backup, which I can
> > always do, but it seems that a simple "svn checkout 970888; ./ant build"
> > might be cleaner. I'm assuming that after updating the code with "svn
> > checkout" I can log the date/time to a file with the output of "svn
> > info".
> >
> > 4) If a revision requires a database update or modification, I would
> > like to know about it in advance, and make sure that manual modification
> > is completed before the upgrade. I'm assuming what I need there should
> > always be found in:
> > https://cwiki.apache.org/confluence/display/OFBTECH/Revisions+Requiring
> > +Data+Migration
> >
> > 5) I would like to update all seed data in place (postgresql) without
> > overwriting the rest of the (non-seed) data. Will executing "./ant
> > run-install-seed" overwrite the EXISTING seed data in a production
> > database without affecting the non-seed data? Or it it only intended
> > for use on an empty database, as all the examples I have found do? If
> > the latter, how do you restore only the NON-seed data after a seed data
> > initialization?
> >
> > Are there any other bear traps or best practices that I should be aware
> > of? Or is this stuff documented somewhere that I have not found? There
> > was a discussion of it (at least the seed vs. demo data issue) about a
> > year ago on this list, but I didn't see these specific questions
> > answered.
> >
> > Or am I overly optimistic about the possibility of updating a production
> > system regularly as OFBiz trunk changes?
> >
> > Thanks in advance.
> >
> >

Matt Warnock

Re: Best practices for updates from trunk

In reply to this post by David E. Jones-2

Thanks David!

At the moment, we only have a few people (4-5 max) that really use the
system, and none of those really "full-time" like a dedicated data entry
person would. So perhaps we can afford to be more lax, or expedite the
testing. We certainly don't need the extensive testing cycle that would
be needed for enterprises with more riding on a "deployment". An
"agile" model would probably work well for us for the time being-- the
question is how best to implement it.

Reading between the lines, it sounds like in-place seed data updates are
either impossible or problematic in practice, and are not recommended.

So perhaps we need to look at freezing the entity defs as you suggest,
then perhaps automating a diff on any entity definition changes to make
sure they are properly scrutinized (and manually implemented) before any
corresponding code update.

--
Matt Warnock <[hidden email]>
RidgeCrest Herbals, Inc.

On Mon, 2010-08-30 at 18:07 -0600, David E Jones wrote:

> Matt,
>
> I wouldn't recommend updating a production instance against the trunk
> without testing. I generally do recommend to clients who are doing
> customizations or building on top of OFBiz that they update against
> the trunk frequently during development, and then stop before
> integration (general system) testing, or at least stop for their
> release candidate branch and continue updating against the OFBiz trunk
> for their development branch.
>
> As for database changes, the Revisions+Requiring+Data+Migration page is
> manually updated and therefore not totally reliable. I'd recommend
> running the Check/Update database stuff in the Entity Engine by
> changing your entityengine.xml file to not automatically update
> anything (ie don't add new tables or columns, etc), and then look at
> the startup log or use webtools to see the differences between the
> current entity definitions and the meta-data in your database.
>
> -David
>

> On Aug 30, 2010, at 3:12 PM, Matt Warnock wrote:
>
> > I run a small enterprise and I doubt our needs are unusual. We would
> > like to run trunk and stay (more or less) current. We're running
> > postgresql as a backend. I'm hoping to automate (as much as possible)
> > the update process. I'm hoping to implement a few things not provided
> > in the standard demo setup.
> >
> > 1) I need to backup the database nightly, so that our daily work doesn't
> > get lost (doh!). I can use pg_dump for that, but of course it backs up
> > the entire database, including seed, admin-user-login, and site-specific
> > data. I could also use the webtools dump, which I assume does the exact
> > same thing but in XML, which is a good deal larger in file size.
> > However, webtools won't write an XML file for an empty table, while
> > pg_dump would write a structure definition for that table. Probably
> > pg_dump would be a good deal faster. Size and speed issues aside, it
> > seems that neither method differentiates in any way between seed and
> > non-seed data. Am I correct here?
> >
> > 2) To effectively use the webtools backup, I would need to automate it
> > from a cron job. Is there an easy way to call ofbiz services from the
> > command line, or do I need to schedule a job within OFBiz to do this
> > kind of thing? What are the pros and cons of a system cron job vs. a
> > scheduled job in OFBiz?
> >
> > 3) I need a log of what version I was running when. For example, if I
> > update weekly, and on Sunday night I roll forward to the latest trunk
> > revision 970999, and it breaks something, I need to have a log that
> > tells me that Friday (when it worked) I was running 970888, so I can
> > roll back to that revision, until I get the kinks worked out with the
> > upgrade. Otherwise I have to restore from a dated backup, which I can
> > always do, but it seems that a simple "svn checkout 970888; ./ant build"
> > might be cleaner. I'm assuming that after updating the code with "svn
> > checkout" I can log the date/time to a file with the output of "svn
> > info".
> >
> > 4) If a revision requires a database update or modification, I would
> > like to know about it in advance, and make sure that manual modification
> > is completed before the upgrade. I'm assuming what I need there should
> > always be found in:
> > https://cwiki.apache.org/confluence/display/OFBTECH/Revisions+Requiring
> > +Data+Migration
> >
> > 5) I would like to update all seed data in place (postgresql) without
> > overwriting the rest of the (non-seed) data. Will executing "./ant
> > run-install-seed" overwrite the EXISTING seed data in a production
> > database without affecting the non-seed data? Or it it only intended
> > for use on an empty database, as all the examples I have found do? If
> > the latter, how do you restore only the NON-seed data after a seed data
> > initialization?
> >
> > Are there any other bear traps or best practices that I should be aware
> > of? Or is this stuff documented somewhere that I have not found? There
> > was a discussion of it (at least the seed vs. demo data issue) about a
> > year ago on this list, but I didn't see these specific questions
> > answered.
> >
> > Or am I overly optimistic about the possibility of updating a production
> > system regularly as OFBiz trunk changes?
> >
> > Thanks in advance.
> >

BJ Freeman

Re: Best practices for updates from trunk

In reply to this post by Matt Warnock

then I suggest best practices is not to do it till a release.
as your db gets larger the processes of verifying everything can take
weeks or months.

do your testing against a copy of your production.

=========================
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
Matt Warnock sent the following on 8/30/2010 5:28 PM:

> Thanks, BJ, but I am looking for best practices on how to do it NOW, not
> the automated component under design for the future. The emails you
> mentioned don't really address any of the questions below. But neither
> does any of the existing docs I have found so far. :-)
>
> Pointers, anyone?
>
> I did try "./ant run-install-seed" on an existing database (previously
> created with "run-install"), it ran without obvious errors and the
> number of rows changed that it reported was several thousand, but less
> than the number with "run-install".
>
> So can it (usually) be safely run on a production database, and will it
> have the intended effect of updating the seed data (if necessary)
> without deleting/overwriting the production data that may refer to that
> seed data? From previous database experience, I know that
> updating/removing/replacing data to which other data points is often a
> problem, to say the least.
>
> Also, are there any pros and cons for putting the OLAP datasource in a
> separate database from the main data source? The existing derby demo
> uses two, but most of the setup tutorials I find are pretty vague on
> this point, but if I point both data sources to the same postgresql
> database, I see no obvious errors. Am i asking for trouble down the
> road? What is the difference between the two, and are there data
> collisions I'm not seeing yet?
>

Matt Warnock

Re: Best practices for updates from trunk

Thanks. Is 10.04 nearing release? Is there an expected release date?
Just curious.
--
Matt Warnock <[hidden email]>
RidgeCrest Herbals, Inc.

On Mon, 2010-08-30 at 20:31 -0700, BJ Freeman wrote:

> then I suggest best practices is not to do it till a release.
> as your db gets larger the processes of verifying everything can take
> weeks or months.
>
> do your testing against a copy of your production.
>
> =========================
> 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
> Matt Warnock sent the following on 8/30/2010 5:28 PM:
>
>
> > Thanks, BJ, but I am looking for best practices on how to do it NOW, not
> > the automated component under design for the future. The emails you
> > mentioned don't really address any of the questions below. But neither
> > does any of the existing docs I have found so far. :-)
> >
> > Pointers, anyone?
> >
> > I did try "./ant run-install-seed" on an existing database (previously
> > created with "run-install"), it ran without obvious errors and the
> > number of rows changed that it reported was several thousand, but less
> > than the number with "run-install".
> >
> > So can it (usually) be safely run on a production database, and will it
> > have the intended effect of updating the seed data (if necessary)
> > without deleting/overwriting the production data that may refer to that
> > seed data? From previous database experience, I know that
> > updating/removing/replacing data to which other data points is often a
> > problem, to say the least.
> >
> > Also, are there any pros and cons for putting the OLAP datasource in a
> > separate database from the main data source? The existing derby demo
> > uses two, but most of the setup tutorials I find are pretty vague on
> > this point, but if I point both data sources to the same postgresql
> > database, I see no obvious errors. Am i asking for trouble down the
> > road? What is the difference between the two, and are there data
> > collisions I'm not seeing yet?
> >

BJ Freeman

Re: Best practices for updates from trunk

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.

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.

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

Re: Best practices for updates from trunk

Understood. Just curious, as I say. Thanks BJ!
--
Matt Warnock <[hidden email]>
RidgeCrest Herbals, Inc.

On Mon, 2010-08-30 at 21:38 -0700, 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.
>
> 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.
>
> 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.

David E. Jones-2

Re: Best practices for updates from trunk

In reply to this post by BJ Freeman

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

Re: Best practices for updates from trunk

In reply to this post by BJ Freeman

On 31/08/2010, at 4:38 PM, BJ Freeman wrote:

> There are a number of bugs that have to be resolved before release

I'm not aware of any bugs that are blocking a release, there may be bugs but not blocking ones.

> remember this is a volunteer effort so there is no full time person doing the patches for the bugs.
>
> 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.

No, the release branch was created 4 months ago. There was never a planned release date, generally it's just when the community thinks it is ready and someone is willing to put the time in to do all the necessary release tasks.

>
> 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.

smime.p7s (3K) Download Attachment

BJ Freeman

Re: Best practices for updates from trunk

In reply to this post by David E. Jones-2

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.
>
>

BJ Freeman

Re: Best practices for updates from trunk

In reply to this post by Scott Gray-2

See my answer to davids email

=========================
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 9:48 PM:

> On 31/08/2010, at 4:38 PM, BJ Freeman wrote:
>
>> There are a number of bugs that have to be resolved before release
>
> I'm not aware of any bugs that are blocking a release, there may be bugs but not blocking ones.
>
>> remember this is a volunteer effort so there is no full time person doing the patches for the bugs.
>>
>> 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.
>
> No, the release branch was created 4 months ago. There was never a planned release date, generally it's just when the community thinks it is ready and someone is willing to put the time in to do all the necessary release tasks.
>
>>
>> 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

Re: Best practices for updates from trunk

In reply to this post by BJ Freeman

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.
>>
>>
>

smime.p7s (3K) Download Attachment

BJ Freeman

Re: Best practices for updates from trunk

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.
>>>
>>>
>>
>

BJ Freeman

Re: Best practices for updates from trunk

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

Re: Best practices for updates from trunk

Administrator

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

Re: Best practices for updates from trunk

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.
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
>

smime.p7s (3K) Download Attachment